Browse files

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

… host

(thanks steadicat).

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 78cff18 commit 7af62f48e33c5e392b6978607e312f4e033f1de4 @jacobian jacobian committed Jul 21, 2005
Showing with 19 additions and 4 deletions.
  1. +19 −4 docs/modpython.txt
@@ -83,10 +83,25 @@ instance. Just use ``VirtualHost`` for that, like so::
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
-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
+ # ...
+ <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

0 comments on commit 7af62f4

Please sign in to comment.