Hi Evert, You are right, I actually intended the question for the Django list - it was a posting error. Thanks for the answer, we did soon figure out to exclude the settings file from any SVN checkins/ checkouts. We will simply apply this rule as it should be simple enough to observe and to make any corrections if a team member overwrites it.
Many thanks, Lloyd On Mon, Aug 16, 2010 at 10:54 AM, Evert Rol <evert....@gmail.com> wrote: > > We have a project at work where myself and a co-developer are setting up > Django. Our version control software of choice is TortoiseSVN. > > > > When doing a project update from SVN, it pulls the server version to the > local project. When checking code in, it overwrites the server version of > the code as expected. > > > > I wish to find out whether Django would work happily this way, as it > requires one to use the django-admin.py tool to create projects and apps. > Would overwriting these files/ directories with server versions compromise > their integrity in a Django setup? > > That's not a Python question, more a Django question or a system-admin > question. You'd be better off using the correct mailing list for that. > > That said, you should be fine, providing you re-sync the databases every > time you 'svn up', to keep your model schema's in the database in sync (you > can use fixtures to sync data in the database). Also the settings files may > differ on the server or the local machines; it's best to keep those out of > SVN, or have a little if-else clause in settings.py that takes care > server-dependent settings. > Otherwise, all your code can (and should) be machine/server agnostic, and > thus easily transportable. > > Evert > > > -- Regards, Sithembewena Lloyd Dube http://www.lloyddube.com
_______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
