Fixed #9434 -- Added a note to the mod_python docs regarding requiring
PythonInterpreter in different VirtualHost blocks that share the same server name. Thanks to Graham Dumpleton for the clarification. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9268 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
c57fe6c3ec
commit
03fcf19fd2
|
@ -160,7 +160,8 @@ instance. Just use ``VirtualHost`` for that, like so::
|
||||||
SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings
|
SetEnv DJANGO_SETTINGS_MODULE mysite.other_settings
|
||||||
</VirtualHost>
|
</VirtualHost>
|
||||||
|
|
||||||
If you need to put two Django installations within the same ``VirtualHost``,
|
If you need to put two Django installations within the same ``VirtualHost``
|
||||||
|
(or in different ``VirtualHost`` blocks that share the same server name),
|
||||||
you'll need to take a special precaution to ensure mod_python's cache doesn't
|
you'll need to take a special precaution to ensure mod_python's cache doesn't
|
||||||
mess things up. Use the ``PythonInterpreter`` directive to give different
|
mess things up. Use the ``PythonInterpreter`` directive to give different
|
||||||
``<Location>`` directives separate interpreters::
|
``<Location>`` directives separate interpreters::
|
||||||
|
|
Loading…
Reference in New Issue