Use a non-Apache WSGI

Currently Apache is only used in the setup to provide access via mod_wsgi, but this seems like it is just another piece of software to manage, configure, upgrade and waste resources.

There are plenty of other wsgi containers ( Gunicorn - http://gunicorn.org/ for instance, or uwsgi - https://github.com/unbit/uwsgi-docs ) that can be hooked up directly from nginx.

Perhaps it would be a good time to remote Apache from the default setup and instead use something more suited for the task with nginx peering directly to the wsgi server.

The issue names no files or tests. Start by reviewing the default setup and its Apache/mod_wsgi and nginx configuration, then compare the proposed WSGI-container options. Done means Apache is removed from the default setup and nginx connects directly to the selected WSGI server.

Written by the indexing model from the issue text.