On 28-Sep-07, at 11:16 PM, Milan Andric wrote:
> Is there some standard practice on a machine that has production code > running in mod_python but also has developers running their django- > python web server? Is that discouraged? I figure a regular user > would not share the same django with mod_python because of .pyc files > and permissions? So developers would maintain separate django > installs. This makes it difficult because then they can't develop > using the same python or need to override the library path? It is not advisable to do development on a production server. And django webserver is to be only used in development. There is no harm whatsover in running multiple sites using a common django install - and a common mod_python - as long as all the users are agreed on the version of django they are using. I run one server with one django which is on the svn head. I give the users 2 days notice before doing an svn up. Nothing prevents them from using their own version of django - but they all have to use the same apache and mod_python. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
