Code

Changes between Version 24 and Version 25 of ServerArrangements


Ignore:
Timestamp:
09/25/06 08:14:39 (8 years ago)
Author:
adrian
Comment:

Added SCGI link and cleaned things up a bit.

Legend:

Unmodified
Added
Removed
Modified
  • ServerArrangements

    v24 v25  
    77See the [http://www.djangoproject.com/documentation/modpython/ official documentation]. 
    88you can also look at the [wiki:django_apache_and_mod_rewrite] small tutorial. 
     9 
    910== Apache with FastCGI == 
    1011 
    1112See the [http://www.djangoproject.com/documentation/fastcgi/ official documentation]. 
    1213 
    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]. 
     14Mac OS X users, see [wiki:OsxFcgi Django with FCGI on OS X]. 
    1615 
    1716== lighttpd with FastCGI == 
     
    1918See the [http://www.djangoproject.com/documentation/fastcgi/ official documentation]. 
    2019 
    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  
    2320Django/lighttpd/FastCGI [http://manuals.textdrive.com/read/book/15 instructions for use on TextDrive shared hosting accounts] are also available. 
    2421 
    2522== Multiple versions with FastCGI == 
    2623 
    27 See [wiki:MultipleVersionsWithFCGI] 
     24See [wiki:MultipleVersionsWithFCGI]. 
    2825 
    2926== Twisted == 
     
    3532See [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. 
    3633 
    37 == Apache and SCGI == 
     34== Apache with SCGI == 
     35 
    3836[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. 
    3937 
     38== lighttpd with SCGI == 
     39 
     40See [http://sayspy.blogspot.com/2006/09/ignorant-newbie-running-django-using.html Running Django using SCGI through LightTPD]. 
     41 
    4042== 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 
     44It'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. 
     45For 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''. 
    4346 
    4447== CGI == 
     
    4851With 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. 
    4952 
    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] 
     53If that hasn't put you off and you still need CGI, take a look at #2407. 
    5154 
    5255== Django built-in development server == 
    5356 
    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 
     57See the [http://www.djangoproject.com/documentation/django-admin/ official documentation].