No, [278] missed the actual bug; this should fix it
git-svn-id: http://code.djangoproject.com/svn/django/trunk@279 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
8a285ec790
commit
2dfea67e34
|
@ -86,7 +86,7 @@ instance. Just use ``VirtualHost`` for that, like so::
|
|||
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::
|
||||
different ``<Location>`` directives seperate interpreters::
|
||||
|
||||
<VirtualHost *>
|
||||
ServerName www.example.com
|
||||
|
|
Loading…
Reference in New Issue