Changes between Version 7 and Version 8 of ConvertingAnApp


Ignore:
Timestamp:
08/13/09 08:53:43 (5 years ago)
Author:
andrew
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ConvertingAnApp

    v7 v8  
    3030 
    3131 
    32 '''Tips on converting a production app under version control''' 
     32'''Converting other installations and servers''' 
    3333 
    34 The convert_to_south command expects to find no existing migrations in your migrations folder so run it on your production environment before you push your initial development database migration to production (making sure both development and production have the same schema and models.py at this point). Alternatively: 
     34The convert_to_south command only works entirely on the first machine you run it on. Once you've committed the initial migrations it made into the database, you'll have to run an extra step on every machine that has a copy of the codebase (make sure they were up-to-date with models and schema first): 
    3535 
    36  * After converting your development apps, commit and push your first migrations to the production server using your preferred vc tool.  
    37  * Run `./manage.py migrate myapp --fake` on production environment to apply the first 'fake' migration.  
     36 * Run `./manage.py migrate myapp 0001 --fake` on each other install to inform South that their databases already match the results of the first migration. 
     37 * Remember that new installations of the codebase after this don't need these steps; you need only do a `syncdb` then a normal `migrate`. 
    3838 
    3939