Gunicorn or Green Unicorn is a Python WSGI HTTP Server for UNIX. It's a
pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server
is broadly compatible with various web frameworks, simply implemented, light on
server resources, and fairly speedy.
The providers of the wsgi relation must provide working_dir, plus optionally
any of the charm's config directives, which will override the current config
for the charm.
- misc ›
- Patrick Hetu firstname.lastname@example.org
How to configure the charm
To deploy a charm with this subordinate it must minimally:
- Provide the wsgi interface.
- Set the
working_dirrelation variable in the wsgi hook.
The configuration of Gunicorn will use the variable pass by
the relation hook first. If there are not define it will
fallback to the global configuration of the charm.
Deployment with python-django for example::
juju bootstrap juju deploy python-django juju deploy postgresql juju deploy gunicorn juju add-relation python-django postgresql:db juju add-relation gunicorn python-django juju expose python-django
Accessing your new django app should be ready at::
To find out the public address of gunicorn/python-django, look for it in
the output of the
juju status command.
I recommend using a reverse proxy like Nginx in front of Gunicorn.
- re-add support for env_extra parameter that was dropped in r3, but with new
standard shell format. e.g. env_extra="FOO=BAR BAZ=QUX". Also supports old
r2 format (env_extra="'foo': 'bar', 'baz': 'qux'") to provide an upgrade
- if upgrading from r1 or r2, the old gunicorn config is removed, leaving just
the custom upstart job.
No backwards incompatible changes.
- Rewrite the charm using python instead of BASH scripts
- add listen_ip configuration variable
Backwards incompatible changes:
- Remove the Django mode since Gunicorn is not recommending it anymore.
- Use Upstart to manage daemons
- no start/stop hook anymore use related charms instead.
- no configuration change directly on the charm anymore, use related charms instead.
- no access logging by default
- exposing a port must now be done in the linked charm instead of this one
- (string) List of environment variables for the wsgi process. e.g. FOO="bar" BAZ="1 2 3"
- (string) IP adresses that Gunicorn will listen on. By default we listen on all of them.
- (string) Background PID file.
- (int) Port the application will be listenning.
- (string) Set an additionnal PYTHONPATH to the project.
- (string) The Access log file to write to.
- (string) The Access log format. Don't forget to escape all quotes and round brackets.
- (int) The maximum number of pending connections.
- (string) Space separated extra settings. For example: --debug
- (string) Switch worker process to run as this group. A valid group id (as an int) or the name.
- (int) Keep alive time in seconds.
- (string) The log file to write to. If empty the logs would be handle by upstart.
- (string) The granularity of Error log outputs.
- (int) The maximum number of requests a worker will process before restarting.
- (int) Timeout of a request in seconds.
- (string) The variable to modify to trigger Gunicorn reload.
- (string) A bit mask for the file mode on files written by Gunicorn. The number 0 means Python guesses the base. Note that this affects unix socket permissions.
- (string) Switch worker processes to run as this user. User id (as an int) or the name.
- (string) Gunicorn workers type. Can be: sync, eventlet, gevent, tornado
- (int) The maximum number of simultaneous clients.
- (int) The number of worker process for handling requests. 0 for count(cpu) + 1
- (string) The name of the WSGI application.