mirror of
https://github.com/django/django.git
synced 2024-12-01 15:42:04 +01:00
Fixed spelling error and reworded mod_python PythonInterpreter section of docs
git-svn-id: http://code.djangoproject.com/svn/django/trunk@285 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
8b58f8b3ae
commit
f8e5df6d7e
@ -83,10 +83,10 @@ instance. Just use ``VirtualHost`` for that, like so::
|
||||
SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin
|
||||
</VirtualHost>
|
||||
|
||||
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>`` directives seperate interpreters::
|
||||
If you need to put two Django installations within the same ``VirtualHost``,
|
||||
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
|
||||
``<Location>`` directives separate interpreters::
|
||||
|
||||
<VirtualHost *>
|
||||
ServerName www.example.com
|
||||
@ -95,13 +95,15 @@ different ``<Location>`` directives seperate interpreters::
|
||||
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>
|
||||
|
||||
The values of ``PythonInterpreter`` don't really matter, as long as they're
|
||||
different between the two ``Location`` blocks.
|
||||
|
||||
Running a development server with mod_python
|
||||
============================================
|
||||
|
Loading…
Reference in New Issue
Block a user