From b4fb448f8387d92832fc70ac58de69c73d5f1729 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Mon, 11 Feb 2013 08:40:11 +0100 Subject: [PATCH] Fixed WSGIPythonPath instruction in deployment docs Partial backport of 3abf6105b6 from master. Refs #19042. --- docs/howto/deployment/wsgi/modwsgi.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/howto/deployment/wsgi/modwsgi.txt b/docs/howto/deployment/wsgi/modwsgi.txt index d669f6d852..2562556ca2 100644 --- a/docs/howto/deployment/wsgi/modwsgi.txt +++ b/docs/howto/deployment/wsgi/modwsgi.txt @@ -61,10 +61,10 @@ Using a virtualenv If you install your project's Python dependencies inside a `virtualenv`_, you'll need to add the path to this virtualenv's ``site-packages`` directory to -your Python path as well. To do this, you can add another line to your -Apache configuration:: +your Python path as well. To do this, add an additional path to your +`WSGIPythonPath` directive, with multiple paths separated by a colon:: - WSGIPythonPath /path/to/your/venv/lib/python2.X/site-packages + WSGIPythonPath /path/to/mysite.com:/path/to/your/venv/lib/python2.X/site-packages Make sure you give the correct path to your virtualenv, and replace ``python2.X`` with the correct Python version (e.g. ``python2.7``).