From 12321ea962128e2c051cb996d7936288f95d1c8f Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Tue, 19 Jul 2005 20:20:38 +0000 Subject: [PATCH] Added 'Running a development server with mod_python' to docs/modpython.txt git-svn-id: http://code.djangoproject.com/svn/django/trunk@223 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/modpython.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/modpython.txt b/docs/modpython.txt index 4c27692b67..0ab37cb1af 100644 --- a/docs/modpython.txt +++ b/docs/modpython.txt @@ -11,6 +11,9 @@ when the server starts. Code stays in memory throughout the life of an Apache process, which leads to significant performance gains over other server arrangements. +Basic configuration +=================== + To configure Django with mod_python, first make sure you have Apache installed, with the mod_python module activated. @@ -60,5 +63,14 @@ Here's a template for an admin configuration:: The only thing different here is the ``DJANGO_SETTINGS_MODULE``. +Running a development server with mod_python +============================================ + +If you use mod_python for your development server, you can avoid the hassle of +having to restart the server each time you make code changes. Just set +``MaxRequestsPerChild 1`` in your ``httpd.conf`` file to force Apache to reload +everything for each request. But don't do that on a production server, or we'll +revoke your Django privileges. + .. _mod_perl: http://perl.apache.org/ .. _mod_python documentation: http://modpython.org/live/current/doc-html/directives.html