= Server arrangements =

Because Django uses [http://www.python.org/peps/pep-0333.html WSGI], it can run on any WSGI-compatible Web server. Here's how to run Django on various server arrangements.

== mod_python ==

See the [http://www.djangoproject.com/documentation/modpython/ official documentation].

== Apache and FCGI ==

Flup (the FCGI wrapper used for this) has a little bug with python 2.3 that will make larger pages stall on access just before end. Make sure you use the newest svn checkout for the flup library, as the bug is fixed in there.

See [http://hugo.muensterland.org/2005/08/03/django-apache-and-fcgi/ Django, Apache and FCGI]. Needs stuff from the [http://hugo.muensterland.org/2005/07/26/running-django-with-fcgi-and-lighttpd/ lighttpd+FCGI documentation].

== lighttpd (via FCGI) ==

See Hugo's excellent tutorials:
 * [http://hugo.muensterland.org/2005/07/26/running-django-with-fcgi-and-lighttpd/ Running Django with FCGI and lighttpd]
 * [http://hugo.muensterland.org/2005/07/27/django-lighttpd-and-fcgi-second-take/ Django, lighttpd and FCGI, second take]

Also see ticket #152.

== Twisted ==

See ticket #172.

== TooFPy ==

See [http://simon.bofh.ms/cgi-bin/trac-toofpy.cgi/wiki/TooFPyAndDjango the description in the trac-wiki] for how to combine them. TooFPy is a pure-python webserver with focus on the creation of web services.

== SCGI ==

Documentation on using [http://www.mems-exchange.org/software/scgi/ SCGI] is welcome!