On Sep 11, 7:05 pm, Mike Ramirez <gufym...@gmail.com> wrote:
> On Friday 11 September 2009 01:52:10 lfrodrigues wrote:
>
>
>
>
>
> > Hi,
>
> > I want to deploy 2 django sites in different subdirectories so I have:
>
> > <VirtualHost *>
> > <Location "/admin">
> > SetHandler python-program
> > PythonHandler django.core.handlers.modpython
> > SetEnv DJANGO_SETTINGS_MODULE admin.settings
> > PythonDebug On
> > PythonOption django.root /admin
> > </Location>
>
> > <Location "/websvc">
> > SetHandler python-program
> > PythonHandler django.core.handlers.modpython
> > SetEnv DJANGO_SETTINGS_MODULE webservice.settings
> > PythonDebug On
> > PythonOption django.root /websvc
> > </Location>
> > </VirtualHost>
>
> > When I go tohttp://host/admin/url/whateversometimes sometimes it
> > works ok, sometimes I get a "page no found" error from the other
> > application " Using the URLconf defined in webservice.urls, ... "
>
> > Any ideas why the applications are overlapping?
>
> Yes, you should set the PythonInterpreter option [1] for mod_python, this
> happened to me when I first used mod_python with multiple projects configured
> this way. The PythonInterpreter value should be a unique string for each
> Location directive. This will force each location to run in it's own
> interpretter. As it is now they are choosing randomly which interpretter to
> use and causing the conflict.
>
> Please. someone if I'm wrong on the reason about how it is working without
> this, correct me.
Yes, you are wrong.
The default for mod_python is that a single interpreter is created for
all VirtualHost's with same ServerName. In other words, not even
distinguished based on listener port. So, no randomness, in selection
of sub interpreter used. The only randomness will be which Django
instance is accessed first and thus which Django settings file takes
precedence. Because Apache is multi process, this might be different
for different processes, thus confusing matters even more.
FWIW, because of this specific issue, mod_wsgi uses a separate sub
interpreter for each mounted WSGI application. Thus, for mod_wsgi by
default the two Django instances would be separated without you
needing to do anything.
Graham
> Hope this helps,
>
> Mike
>
> [1]http://www.modpython.org/live/mod_python-3.2.5b/doc-html/dir-other-pi...
> --
> ignorance, n.:
> When you don't know anything, and someone else finds out.
>
> signature.asc
> < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
