Usage

Add a part to your buildout.cfg like so:

[buildout]
parts=uwsgi

[uwsgi]
recipe=shaunsephton.recipe.uwsgi

Running the buildout will download and compile uWSGI and add an executable with the same name as your part in the bin/ directory. In this case bin/uwsgi. It will also create a uwsgi.xml configuration file in a parts directory with the same name as your part. In this case bin/uwsgi/uwsgi.xml.

This allows you to start a uWSGI process configured by the generated XML file, i.e.:

$ ./bin/uwsgi --xml parts/uwsgi/uwsgi.xml

The generated XML configuration includes pythonpath directives referencing the various Python eggs installed by Buildout allowing uWSGI to utilize them.

You can specify any and all additional uWSGI configuration options as additional options of the Buildout part. For instance to specify a socket and module and to enable the master process add socket, module and master options to the buildout part, i.e.:

[buildout]
parts=uwsgi

[uwsgi]
recipe=shaunsephton.recipe.uwsgi
socket=127.0.0.1:7001
module=my_uwsgi_package.wsgi
master=True

You can also provided a set of eggs explicitly using the eggs option, i.e.:

[buildout]
parts=uwsgi

[uwsgi]
recipe=shaunsephton.recipe.uwsgi
eggs=my_uwsgi_package

Created By

1. Shaun Sephton

Contributors

1. mooball

0.0.9 (2011-09-21)

1. Dynamic option resolution.

2. Moved conf to parts.

3. Regenerate XML on update to catch updated eggs.