tranchitella.recipe.wsgi 0.4

Buildout recipe to create paste.deploy entry points for mod_wsgi

tranchitella.recipe.wsgi

This recipe creates a paste.deploy entry point for mod_wsgi.

Usage

This is a minimal ‘’buildout.cfg’’ file which creates a WSGI script mod_wsgi can use:

[buildout]
parts = wsgi

[wsgi]
recipe = tranchitella.recipe.wsgi
eggs = myapplication
config-file = ${buildout:directory}/etc/deploy.ini
environ =
    CHAMELEON_CACHE=true
    CHAMELEON_STRICT=true

This will create a small python script in the bin directory called ‘’wsgi’’ which mod_wsgi can load. You can also use the optional ‘’extra-paths’’ option to specify extra paths that are added to the python system path.

You may also use the ‘’script-name’’ option to specify the name of the generated script file, if ‘’wsgi’’ is unsuitable.

The apache configuration for this buildout looks like this::

WSGIScriptAlias /mysite /path/to/buildout/bin/wsgi

<Directory /home/me/buildout>
    Order deny,allow
    Allow from all
</Directory>

This recipe does not fully install packages, which means that console scripts will not be created. If you need console scripts you can add a second buildout part which uses zc.recipe.egg to do a full install.

Changes

0.4 (2010-04-26)

• Removed dependency on Chameleon.

• Defaults to the part name for the script name instead of “wsgi”.

• Added tests.

0.3 (2010-04-09)

• Add a script-name option to specify the name of the wsgi script to generate. (Dan Fairs, [e-mail])

• Fix a bug where ‘None’ would appear in the generated file if no environ was specified. (Dan Fairs, [e-mail])

0.2 (2010-04-06)

• Install again on update, otherwise the wsgi script is not updated unless it is explicitly removed.

0.1 (2010-02-17)

• First public release.