= 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 DjangoUsingFlup for more. 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]. Mac OS X users see [wiki:OsxFcgi Django with FCGI on OS X] -- How to get Django up and running with FCGI and the Mac OS X default Apache 1.3 == 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. Django/lighttpd/FastCGI instructions for use on TextDrive shared hosting accounts are available [http://manuals.textdrive.com/read/book/15 here]. == 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. == Apache and SCGI == [http://www.mems-exchange.org/software/scgi/ SCGI] can be used with Apache [https://simon.bofh.ms/cgi-bin/trac-django-projects.cgi/wiki/DjangoScgi#preview like this]. It builds on stuff from the Apache+FCGI documentation above. == Django behind/inside Zope == Not really a server arrangement ''per se'', I've found a way to query a Django site from Zope or Plone and return the result. This allows you to include a Django site inside a pre-existing Zope/Plone site. Good for custom content that you don't want to use existing Zope technologies to develop. For the code, see [http://pastebin.com/390301 this Pastebin] or drop an email to jeff (at) bitprophet (dot) org.