We have used South for staging and production for a while now (what good
otherwise it is?). Our deployment flow is something on the lines of:
(Note: Tasks are automated using Fabric)
1. Have a production_settings.py file in the git repo
2. Migrations are also commited to the repo
3. When changes
I started a django 1.6 project in a virtual environment (Debian, python
2.7) and installed south.I created the models, database, performed many
migrations and it all worked well. All with mysql.
I then split the settings.py file into production and development and set
up a production server on ap
2 matches
Mail list logo
