On 04/25/2015 11:15 AM, Javier Guerra Giraldez wrote: > On Sat, Apr 25, 2015 at 12:08 PM, Timothy W. Cook <t...@mlhim.org> > wrote: >> >> On Sat, Apr 25, 2015 at 9:48 AM, Jorge Andrés Vergara Ebratt >> <javebr...@gmail.com> wrote: >>> >>> Are you using version control like GIT? I save the migration >>> folder with the __init__.py in GIT, nothing else, because al the >>> migrations will be diferent in the diferent servers. >>> >> >> This is probably what I should have done. I have been saving them >> all to the git repo. > > > with South i used to save them to the repo too and push whole to > production. haven't tried Django migrations yet; is there any > difference that make this more appropriate? > > if you don't store migrations, then you have to generate them on > each production update, right? if so, wouldn't they count as > untested code? how about manually tweaked, or data migrations?
Migrations should be committed to VCS in both South and in Django migrations. Carl -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/553C1F83.60105%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
