The thing is, you should be able to catch those issues when migrating locally on you development machines. In that case, just fix the migration and then it should work perfectly in production. You can always add certain values in the migration scripts themselves.
-- Regards,
Andréas
2016-02-10 14:51 GMT+01:00 Tobias Dacoir <falc410@gmail.com>:
Thanks for sharing your workflow. Sounds simple enough and is more or less a scripted version of what I had in mind all along.--
About the manual intervention: At some points during development we had to provide a one-time manual entry when Django was migrating the database, either by adding or removing properties to existing models. This shouldn't happen after we go live with 1.0 - hopefully. We always have ideas for new features to be build in :)
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2566cd3d-478b-4276-aba7-3917141ae104%40googlegroups.com.
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALXYUbnxgf_BAbofbevV0Etxn9Dv-zjK3NAh3AdE7JHOHoN2ew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment