>> 3. Set up an Apache server for development (as indicated in the >> mod_python documentation). This has the disadvantages that I would >> need to manually set up a VirtualHost in apache2.conf for each project >> everytime one is added and also that they would need to maintain a >> hosts file on their workstations (we don't have an internal DNS >> server.) >> >> At a previous job we had dozens of developers working on various bits to a java/j2ee project running on weblogic. Each developer had their own instance to develop on, spread across a couple of dev servers. One would have http://devserver:8001, the next 8002, etc
They used scripts to start and stop their server as needed, without interfering with anybody else. Basically they would call something like "startserver <PORT>" and off it would go. The advantage of this is, as we added things, we only had to edit one script. All configuration files were setup when the server started, again to keep up with changes. It might be overkill for what you need, but it's one way to do your idea #3. I think it would be pretty straightforward to do with django Just an idea --B --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
