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 need to be deployed, a git pull is executed on the server
4. production_settings.py is renamed to settings.py (simple "mv" command on linux)
5. The fabfile contains a list of apps that need to be migrated (ex: ['app1', 'app2', 'aap2'])
6. Migrations are then executed for the apps in the list on the server (./manage.py migrate <app>)
(Note: branches are used to segregate dev and production migrations)
-- (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 need to be deployed, a git pull is executed on the server
4. production_settings.py is renamed to settings.py (simple "mv" command on linux)
5. The fabfile contains a list of apps that need to be migrated (ex: ['app1', 'app2', 'aap2'])
6. Migrations are then executed for the apps in the list on the server (./manage.py migrate <app>)
(Note: branches are used to segregate dev and production migrations)
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e8bc6af7-7939-445d-b062-6e30af2a460e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment