FastcgiOrModpython
PythonCGI
Flup
ModPython
WSGI
Django
Lighttpd
(dynamic) FastCGI on Apache
- 3 types of applications
- dynamic: FastCGI-application will be started and stopped as neccessary by FastCGI process-manager (and can be configured via FastCgiConfig, i.e. instances of the app don't have to be set-up via FastCgiExternalServer(external), or FastCgiServer (static)
- FastCgiExternalServer filename -host hostname:port [option ...]
- URIs? that Apache resolves to this filename will be handled by this external FastCGI application.
- The FastCGI that serves on the specified port does not need to be started via that filename.
set-up dynamic FastCGI
trying to get something like
Simpler Apache FCGI Django to work...
- http://forum.dreamhosters.com/troubleshooting/70110-Python-FASTCGI-will-not-start.htm
- describes a problem I got when calling the fcgi-script directly - but no direct solution
- Apache softlimit
- rewrite.log does not really help
- web.err gives
- [Mon Mar 12 22:54:42 2007] [error] [client ...IP...] FastCGI: "ExecCGI Option" is off in this directory: /zitate/
- well...
- Dynamic FastCGI applications require the ExecCGI? option be enabled (see the Options directive) in the application's directory. [1]
- after adding
<Directory /home/path/to/django.fcgi>
Options +ExecCGI -Indexes
</Directory>
[Mon Mar 12 23:12:33 2007] [warn] FastCGI: (dynamic) server "/home/.../django.fcgi" restarted (pid 27940)
ERROR: No module named flup
Unable to load the flup package. In order to run django
as a FastCGI application, you will need to get flup from
http://www.saddi.com/software/flup/ If you've already
installed flup, then make sure you have it in your PYTHONPATH.
- ahhh
- adding Flup to sys.path helps
- PYTHONPATH
- Actually, modules are searched in the list of directories given by the variable sys.path which is initialized from the directory containing the input script (or the current directory), PYTHONPATH and the installation-dependent default. [2]