I don't see the point of #1 either. It would work well for your first deployment to production, but what happens when you change the database schema after that? You can run initial migrations, because many of the tables already exists. Its the reason South exists in the first place.
So I agree with using #2. In addition to the points Joey makes, it also means you have metadata about how your database schema has changed over time. _Nik On 2/4/2013 9:38 AM, Joey Espinosa wrote: > I've read two distinct points on the matter: > > 1) Don't push migrations to production. Instead, delete all migrations > and run a single "--initial" migration, and push that to production. > That way you keep production clean and free of the clutter from past > schema mistakes and changes. > > 2) Push all migrations to production. That way you are able to > duplicate all database changes on your development box, and you can > keep track of all the changes that have been made to your production > server. Also, if something goes wrong (because production data is > different than test or development data), you can still rollback as > many migrations as you need to troubleshoot the problem, correct it, > and move forward. > > I tend to lean heavily toward #2. I've never agreed with (or seen the > point of) #1. However, if someone would be so kind as to provide a > more specific (or detailed) argument in favor of #1, I'd be glad to > hear it. > > -- > Joey "JoeLinux" Espinosa* > * > <http://therealjoelinux.blogspot.com><http://twitter.com/therealjoelinux><http://about.me/joelinux> > > > On Mon, Feb 4, 2013 at 12:25 PM, coded kid <duffleboi...@gmail.com > <mailto:duffleboi...@gmail.com>> wrote: > > Please I would like to know if it's advisable to push South migration > folder in development environment to git repo before cloning it from > repo to production server. Or one should delete the South migration > folder and push to git repo. Hope you get my point? > > -- > 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 > <mailto:django-users%2bunsubscr...@googlegroups.com>. > To post to this group, send email to django-users@googlegroups.com > <mailto:django-users@googlegroups.com>. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > 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 http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
