test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added note about using different settings modules in the same virtual host 

(thanks steadicat).


git-svn-id: http://code.djangoproject.com/svn/django/trunk@277 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2005-07-21 17:37:36 +00:00
parent 78cff1837a
commit 7af62f48e3
1 changed files with 19 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/modpython.txt
View File

@ -83,10 +83,25 @@ instance. Just use ``VirtualHost`` for that, like so::
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
</VirtualHost>
Don't put two Django installations within the same ``VirtualHost``. Due to the
way mod_python caches code in memory, your two Django installations will
conflict. If you can think of a way to solve this problem, please file a ticket
in our ticket system.
If you need to put two Django installations within the same ``VirtualHost``,
you'll see problems due to the way mod_python caches code in memory. To fix
this problem, you'll need to use the ``PythonInterpreter`` directive to give
different ``<Location>``s seperate interpreters::
<VirtualHost *>
ServerName www.example.com
# ...
<Location "/something">
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.main
PythonInterpreter myproject_main
</Location>
<Location "/admin">
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
PythonInterpreter myproject_admin
</Location>
</VirtualHost>
Running a development server with mod_python
============================================