Re: django.contrib apps migrations

2016-05-26 Thread McKinley
I managed to use fixtures to suit my needs for maintaining concurrency across admin app with collaborators. On Sunday, May 15, 2016 at 2:42:00 AM UTC-7, Michal Petrucha wrote: > > On Fri, May 13, 2016 at 01:01:22PM -0700, McKinley wrote: > > Hi Michal, > > > > I know the django.contrib migrati

Re: django.contrib apps migrations

2016-05-15 Thread Michal Petrucha
On Fri, May 13, 2016 at 01:01:22PM -0700, McKinley wrote: > 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

Re: django.contrib apps migrations

2016-05-13 Thread McKinley
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 gettin

Re: django.contrib apps migrations

2016-05-12 Thread Michal Petrucha
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 > installatio

django.contrib apps migrations

2016-05-12 Thread Sean McKinley
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? -- You received this message because you are subscribed to the Goo