Changes between Version 24 and Version 25 of ServerArrangements
- Timestamp:
- Sep 25, 2006, 10:14:39 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ServerArrangements
v24 v25 7 7 See the [http://www.djangoproject.com/documentation/modpython/ official documentation]. 8 8 you can also look at the [wiki:django_apache_and_mod_rewrite] small tutorial. 9 9 10 == Apache with FastCGI == 10 11 11 12 See the [http://www.djangoproject.com/documentation/fastcgi/ official documentation]. 12 13 13 Mac OS X users, see [wiki:OsxFcgi Django with FCGI on OS X] -- How to get Django up and running with FastCGI and the Mac OS X default Apache 1.3 14 15 Legacy documentation (i.e., unofficial docs written before the official docs were released) is available here: [http://hugo.muensterland.org/2005/08/03/django-apache-and-fcgi/ Django, Apache and FCGI] and [http://hugo.muensterland.org/2005/07/26/running-django-with-fcgi-and-lighttpd/ lighttpd+FCGI documentation]. 14 Mac OS X users, see [wiki:OsxFcgi Django with FCGI on OS X]. 16 15 17 16 == lighttpd with FastCGI == … … 19 18 See the [http://www.djangoproject.com/documentation/fastcgi/ official documentation]. 20 19 21 Legacy documentation (i.e., unofficial docs written before the official docs were released) is available here: [http://hugo.muensterland.org/2005/07/26/running-django-with-fcgi-and-lighttpd/ Running Django with FCGI and lighttpd] and [http://hugo.muensterland.org/2005/07/27/django-lighttpd-and-fcgi-second-take/ Django, lighttpd and FCGI, second take].22 23 20 Django/lighttpd/FastCGI [http://manuals.textdrive.com/read/book/15 instructions for use on TextDrive shared hosting accounts] are also available. 24 21 25 22 == Multiple versions with FastCGI == 26 23 27 See [wiki:MultipleVersionsWithFCGI] 24 See [wiki:MultipleVersionsWithFCGI]. 28 25 29 26 == Twisted == … … 35 32 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. 36 33 37 == Apache and SCGI == 34 == Apache with SCGI == 35 38 36 [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. 39 37 38 == lighttpd with SCGI == 39 40 See [http://sayspy.blogspot.com/2006/09/ignorant-newbie-running-django-using.html Running Django using SCGI through LightTPD]. 41 40 42 == Django behind/inside Zope == 41 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. 42 For the code, see [http://bitprophet.org/code/django_to_zope.py this partly documented file]. It's in a temporary location for the time being; when I get a blog set up, I plan to complete the explanation and post it. For more info, drop an email to ''jeff (at) bitprophet (dot) org''. 43 44 It's possible 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. It's good for custom content that you don't want to use existing Zope technologies to develop. 45 For the code, see [http://bitprophet.org/code/django_to_zope.py this partly documented file]. It's in a temporary location for the time being; for more info, e-mail ''jeff (at) bitprophet (dot) org''. 43 46 44 47 == CGI == … … 48 51 With traditional CGI, the program which will be run -- in this case, Django plus a Django-powered application -- is loaded from disk into memory each time a request is served, which results in a significant amount of processing overhead and much slower responses. FastCGI and SCGI, in contrast, load the code only once -- when the server starts up -- and keep it in memory as long as the server is running, resulting in much faster responses. 49 52 50 If that hasn't put you off and you still need CGI, take a look at [http://code.djangoproject.com/ticket/2407 ticket 2407]53 If that hasn't put you off and you still need CGI, take a look at #2407. 51 54 52 55 == Django built-in development server == 53 56 54 By default the development server that comes with Django will only accept connections on the localhost interface (127.0.0.1). To have it listen on the proper network interface, you can start the server like this: 55 56 python manage.py runserver 0.0.0.0:8000 57 See the [http://www.djangoproject.com/documentation/django-admin/ official documentation].