Thanks for the reply. Thanks for the advice. We should include the migrate command into our git hook as well. But like I said, sometimes it's not always possible as manual interaction is required. At least for 1.0 our model should not change much, except for future extensions and new models.
We also have a development / test server that is a direct clone of the future live server. However I still don't have the workflow laid out. Should we use KISS and just upload a zip of our new version and just replace the whole folder on the live server with the new code and issue an Apache restart afterwards (not even sure that this is needed in order to pick up the new code)? -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a8ae9869-83cb-4023-a884-91ebf8190724%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
