Hi Michal, I know the django.contrib migrations reside within my virtualenv. What if I wanted a fellow developer to have access to these migrations without sharing the same django install. If i have a colleague working on their own machine and they git pull my django project, they aren't getting my admin and auth migrations so aren't we working on different data afterwards?
On Thursday, May 12, 2016 at 10:54:51 PM UTC-7, Michal Petrucha wrote: > > On Thu, May 12, 2016 at 04:55:46PM -0700, Sean McKinley wrote: > > Django 1.7+ noob here. Are you supposed to to track the migrations > > performed within the django.contrib apps? How do you deploy to > production > > on a different machine without grabbing these migrations from the django > > installation? > > Hi Sean, > > You don't have to do anything special – the packages in django.contrib > ship with their own migrations, which means that once you add some of > them into your INSTALLED_APPS, the next time you run ./manage.py migrate, > the migrations runner will simply pick up those migrations from where > they are, and apply them. > > If I may ask, what did you mean by grabbing those migrations? Django > expects each migration to reside inside the package to which it > belongs, so if you take a migration from one of the contrib packages, > and put it somewhere else, it probably won't work correctly, because > it will no longer be inside the respective contrib package. > > Cheers, > > Michal > -- 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/23b346e5-82f2-4691-9492-ed596b189551%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
