ch24lev1sec5.html

Q&A

Q. If I decide to do development on an Apache server with mod_python, how do I keep from having to restart the server every time I make a change?
A. The reason you have to restart the server to apply the updated code is that mod_python caches loaded Python code. If you add the following setting to your Apache httpd.conf file, it will force Apache to reload everything for each request. You can use this setting for development, but you should never use it for a production server:
MaxRequestPerChild 1

Q. Why can't I see error messages in my Apache error_log?
A. Django handles errors using its own error-handling system.
Q. Can I use Django with FastCGI?
A. Yes. You can use Django with FastCGI, but you need to install the flup Python Library to deal with FastCGI. Then you can use the runfcgi utility provided with Django. You can find more information about flup at http://trac.saddi.com/flup. You can find more information about runfcgi at www.djangoproject.com/documentation/fastcgi.

Q.	If I decide to do development on an Apache server with mod_python, how do I keep from having to restart the server every time I make a change?
A.	The reason you have to restart the server to apply the updated code is that mod_python caches loaded Python code. If you add the following setting to your Apache `httpd.conf` file, it will force Apache to reload everything for each request. You can use this setting for development, but you should never use it for a production server: MaxRequestPerChild 1

Q.	Why can't I see error messages in my Apache error_log?
A.	Django handles errors using its own error-handling system.
Q.	Can I use Django with FastCGI?
A.	Yes. You can use Django with FastCGI, but you need to install the `flup` Python Library to deal with FastCGI. Then you can use the `runfcgi` utility provided with Django. You can find more information about `flup` at `http://trac.saddi.com/flup`. You can find more information about `runfcgi` at www.djangoproject.com/documentation/fastcgi.