Option number three is the most common, and what we use here at work (even though it's PHP, the principle is the same). With one difference, the source code for each individual lies on the server. Here where I work, each user has a /home/ sub-directory on a server with Apache, PHP, Mysql and Subversion. The /home/ directories are shared using Samba.
I used to use Linux, and now I use Windows, but the principle is the same. My "home" on the server appears on My Network Locations, I just open files there and edit them. Apache is setup to rewrite calls to http://ser.ver.ip/home/my_name/my_project/ to filesystem's /home/my_name/my_project/. So, when I edit a file on my /home/, I don't break anyone else's copy and I can see the changes by loading "/my_" URLs. From time to time, we commit things to a SVN repository. This is *crucial*. You mentioned that you don't have much experience with version control software, so it's a good chance to learn it :) Because with SVN, all I have to do is "svn update" (or use Tortoise, it's very good!) and get the changes done by anyone else. If you have, your QA team or testers can checkout a copy to test the latest developments. With Python and Django, nothing much changes from this process. You still can have Apache rewriting to shared directories. And maybe pylint running daily on the code... On 3/16/06, tonemcd <[EMAIL PROTECTED]> wrote: > > 3. People run their own local django installations, and commit changes > to a development server for testing before those changes are sent to > the deployment server. This means each individual user machine has to > have access to the databases and keeps a copy of the source on their > machine. It also means a lot of django trunk duplication on each > machine (I guess we could do an 'svn up' where the target is our own > django installation on the server - nice thought!). We have very little > experience of using svn etc however. -- Julio Nobrega - http://www.inerciasensorial.com.br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
