greins 0.2.1

greins

Options are the same as for Gunicorn with one exception: the single APP_MODULE argument is replaced by APP_DIR, a directory containing python source files as described in the following section.

Application Configuration

Applications should be configured by placing a python source file in the configuration directory. This file should populate a dictionary in the global scope called mounts which maps address prefixes (or ‘mount points’) to WSGI handler functions.

These files are evaluated just like a Gunicorn config file. Server hooks are valid in these configuration files and work as in Gunicorn. Other options, such as logging and worker configuration, are ignored and should be configured globally for the Greins application.

As a convenience, a file name myapp which does not define any mounts will try to import myapp:application and mount it underneath the path /myapp.

It should be possible to write an application for Gunicorn and then place a Gunicorn configuration file inside the configuration directory for Greins to begin using it within Greins immediately, provided that the config file name matches a module in the python path which exports application as a WSGI callable.

Examples

The examples directory runs a single greins application from the file test.py which demonstrates loading several routes as well as using the gunicorn server hooks. To run the examples, launch greins from the directory above examples with:

$ greins examples

The greins command accepts gunicorn options. For example:

$ greins -kgevent -b0.0.0.0:8080 examples