Code

Changes between Version 221 and Version 222 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
08/08/08 18:25:49 (6 years ago)
Author:
jonathan_ultis
Comment:

more detail on fixing a simple lighttpd config for change 8015.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v221 v222  
    229229 
    230230Notes: 
     231 
     232 
    231233 1. It is important that you remember to use XML format in the first step of this process. We are exploiting a feature of the XML data dumps that makes porting floats to decimals with SQLite possible. 
    232234 2. In the second step you will be asked to confirm that you are prepared to lose the data for the application(s) in question. We restore this data in the third step, of course. 
     
    10101012reverse URL construction. To overcome this problem, you can use the 
    10111013`FORCE_SCRIPT_NAME` Django setting to force the value to whatever you want. 
     1014 
     1015If you're using the basic lighttpd configuration from our site, you'll want: 
     1016 
     1017{{{ 
     1018FORCE_SCRIPT_NAME="/" 
     1019}}} 
     1020 
    10121021This is a bit of a hacky solution, since it requires changing the project 
    10131022settings every time you change the URL prefix. However, there's nothing that