Skip to main content

WSGI Server with SSL, code reloading.

Project description

A backgrounding front-end over cherrypy (builtin), twisted.web, circuits, spawning, fapws3, and werkzeug, With server-independent support for code reloading and pid file management.


Run a server in the foreground after importing as the application instance:

wsgid --application

Run a server in the foreground after importing and calling mywebapp.create_app as the application factory:

wsgid --application_factory mywebapp.create_app

Run a server using the pidfile after importing and calling mywebapp.create_app as the application factory:

wsgid --application_factory mywebapp.create_app --pidfile

Stop a server using the pidfile

wsgid --pidfile --stop

Use twisted.web’s server to display builtin hello-world:

wsgid --server=twistedweb

All these options have short versions, and can override defaults in config files or the environment.

Using config files

Ini-style config files can be used to provide any of the options available. For example, myserver.ini:

[ config ]

pidfile =
application_factory = mywebapp.crate_app

And then:

wsgid -c myserver.ini

Is equivalent to the above examples. Note that the actual section titles in the config file are ignored, and the file is essentially flattened.

Using the environment

Additionally any config variable can be overriden using the environment variables. The variable name is uppercased, and prefixed with WSGID_ to avoid collisions with other apps for common names. For example:


Is equivalent to passing the –pidfile on the command line.

Using the Werkzeug Debugger

Passing the option -d/–debug will wrap your WSGI application in the Werkzeug debugger. It is not recommended to do this in production:

wsgid --application --foreground --debug

Using SSL

The default CherryPy backend supports SSL, and this is enabled using the two options –ssl_certificate/-C with –ssl_private_key/-K, To generate these as an example:

openssl genrsa 1024 > host.key
openssl req -new -x509 -nodes -sha1 -days 365 -key host.key > host.cert

Then you can run your server like:

wsgid --application --foreground --ssl_certificate=host.cert --ssl_private_key=host.key

Complete options

Usage: wsgid [options]

-h, --help

show this help message and exit

-c CONFIG_FILE, --config_file=CONFIG_FILE

The configuration file

-p PIDFILE, --pidfile=PIDFILE

The PID file

-s, --stop

Stop the server.


The WSGI Applciation instance to import


The WSGI Applciation factory to import

-d, --debug

Run in the werkzeug debugger.

-P PORT, --port=PORT

The port to listen on.

-H HOST, --host=HOST

The host to listen on.

-N, --no_reloader

Do not use the reloader.

-L LOGDIR, --logdir=LOGDIR

The directory for logs.

-w WORKDIR, --workdir=WORKDIR

The working directory for the daemon.


The server name


The ssl certificate


The ssl private key


Path to a virtualenv to use

-v, --verbose

Verbose logging

-T, --no_log_stdout

Do not log on stdout

-O SERVER, --server=SERVER
Server type to use, can be:

cherrypy (default) twistedweb circuitsweb fapws3 spawningweb wz

-X, --dumb

Run a dumb server. Does not handle pidfiles/logs/etc.

Developer Information

Repository/tracker/wiki/etc at:

Latest tip package:

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

wsgid-0.9.tar.gz (30.6 kB view hashes)

Uploaded Source

Built Distribution

wsgid-0.9.linux-i686.tar.gz (64.9 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page