cykooz.recipe.pastewsgi 0.6.1

Buildout recipe to create paste.deploy entry points for mod_wsgi or uwsgi

cykooz.recipe.pastewsgi

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

This project is a fork of recipe tranchitella.recipe.wsgi (https://pypi.python.org/pypi/tranchitella.recipe.wsgi) originally created by Tranchitella Kft. Forked to add new options.

Usage

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

[buildout]
parts = wsgi

[wsgi]
recipe = cykooz.recipe.pastewsgi
eggs = myapplication
config-file = ${buildout:directory}/etc/deploy.ini
environ =
    CHAMELEON_CACHE=true
    CHAMELEON_STRICT=true
initialization =
    import logging
    logging.info('Run myapplication')

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. Or you may use the target option to specify a full path of the generated script file.

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.6.1 (2015-06-25)

• Fixed a bug when using Python 3.x.

• Added the initialization option target that can be used to specify a full path of generated script.

0.5 (2014-05-20)

• Create fork of tranchitella.recipe.wsgi == 0.4

• Add an initialization option to specify code for additional initialization