<Location "/dj/ham">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE ham.settings
PythonPath "['/usr/local/apache2/haredocs/dj'] + sys.path"
PythonDebug On
</Location>
<Location "/dj/spam">
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE spam.settings
PythonPath "['/usr/local/apache2/haredocs/dj'] + sys.path"
PythonDebug On
</Location>
What happens is that every now and then I get a Django 404 error showing the wrong urls.py patterns. E.g., sometimes http://localhost/dj/ham 404's and shows the url patterns for the spam project, and sometimes http://localhost/dj/spam 404s and shows the url patterns for ham (FYI, I'm running with Django debug on). If I restart Apache, then the 1st request always works, then its all a bit hit & miss after that.
My guess is that the DJANGO_SETTINGS_MODULE is set once only per server process, then its pot-luck which process and which DJANGO_SETTINGS_MODULE setting any particular request gets.
Is the above config. the best approach? Can I force DJANGO_SETTINGS_MODULE to be set in a server process each time a request is received. Is it reasonable to run two or more different Django projects in the same Apache instance?
One thought occurs to me is to use the same settings.py for both projects, then put a big switch at the top, depending on the URL, but this seems silly, duplicating Apache configs & Django's URL mapping.
Thanks for any tips...
|
-- Les Smithson <[EMAIL PROTECTED]> Open Network Solutions Ltd |
signature.asc
Description: This is a digitally signed message part
