Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

For example uwsgi. It's easy to install and configure. There is also gunicorn.

The benefit is that uwsgi can run the master process and workers and will do some process maintenance for you. uWSGI is written in C so I bet it's faster than runserver.

For example uwsgi. uwsgi, that's what we use. It's easy to install and configure. There is also gunicorn.gunicorn. On the front-end we use nginx.

The benefit is that uwsgi can run the master process and workers and will do some process maintenance for you. uWSGI is written in C so I bet it's faster than runserver.

For example uwsgi, that's what we use. It's easy to install and configure. There is also gunicorn. On the front-end we use nginx.

The benefit is that uwsgi can run the master process and workers and will do some process maintenance for you. uWSGI is written in C so I bet it's faster than runserver.

To ease the transition you could just comment out that message in the template and continue using the runserver in the production mode until you have uwsgi and nginx installed (or mod_wsgi + Apache).

For example uwsgi, that's what we use. It's easy to install and configure. There is also gunicorn. On the front-end we use nginx.

The benefit is that uwsgi can run the master process and workers and will do some process maintenance for you. uWSGI is written in C so I bet it's faster than runserver.

To ease the transition you could just comment out that message in the template and continue using the runserver in the production mode until you have uwsgi and nginx installed (or mod_wsgi + Apache).Apache if you can't use nginx for some reason).