From ff4609b686d548b6a4050ee505d30bf96ce6245c Mon Sep 17 00:00:00 2001 From: Jacob Kaplan-Moss Date: Tue, 7 Apr 2009 19:11:20 +0000 Subject: [1.0.X] Fixed #10714 - made mod_wsgi recommendation consistent across deployment documentation, and removed duplicate modwsgi nav link. Backport of r10411 and r10413 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@10416 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/deployment/modpython.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/howto/deployment/modpython.txt') diff --git a/docs/howto/deployment/modpython.txt b/docs/howto/deployment/modpython.txt index 331515bdd8..9ba1c2f9fb 100644 --- a/docs/howto/deployment/modpython.txt +++ b/docs/howto/deployment/modpython.txt @@ -6,8 +6,9 @@ How to use Django with Apache and mod_python .. highlight:: apache -Apache_ with `mod_python`_ currently is the preferred setup for using Django -on a production server. +The `mod_python`_ module for Apache_ can be used to deploy Django to a +production server, although it has been mostly superseded by the simpler +:ref:`mod_wsgi deployment option `. mod_python is similar to (and inspired by) `mod_perl`_ : It embeds Python within Apache and loads Python code into memory when the server starts. Code stays in -- cgit v1.3