How to use Django with uWSGI¶
uWSGI is a fast, self-healing and developer/sysadmin-friendly application container server coded in pure C.
The uWSGI docs offer a tutorial covering Django, nginx, and uWSGI (one possible deployment setup of many). The docs below are focused on how to integrate Django with uWSGI.
The uWSGI wiki describes several installation procedures. Using pip, the Python package manager, you can install any uWSGI version with a single command. For example:
# Install current stable version.
$ pip install uwsgi
# Or install LTS (long term support).
$ pip install http://projects.unbit.it/downloads/uwsgi-lts.tar.gz
Some distributions, including Debian and Ubuntu, ship an outdated version
of uWSGI that does not conform to the WSGI specification. Versions prior to
1.2.6 do not call
close on the response object after handling a
request. In those cases the
signal isn’t sent. This can result in idle connections to database and
uWSGI operates on a client-server model. Your Web server (e.g., nginx, Apache) communicates with a django-uwsgi “worker” process to serve dynamic content. See uWSGI’s background documentation for more detail.
Configuring and starting the uWSGI server for Django¶
Here’s an example command to start a uWSGI server:
uwsgi --chdir=/path/to/your/project \
--env DJANGO_SETTINGS_MODULE=mysite.settings \
--master --pidfile=/tmp/project-master.pid \
--socket=127.0.0.1:49152 \ # can also be a file
--processes=5 \ # number of worker processes
--uid=1000 --gid=2000 \ # if root, uwsgi can drop privileges
--harakiri=20 \ # respawn processes taking more than 20 seconds
--max-requests=5000 \ # respawn processes after serving 5000 requests
--vacuum \ # clear environment on exit
--home=/path/to/virtual/env \ # optional path to a virtualenv
--daemonize=/var/log/uwsgi/yourproject.log # background the process
This assumes you have a top-level project package named
within it a module
mysite/wsgi.py that contains a WSGI
object. This is the layout you’ll have if you ran
startproject mysite (using your own project name in place of
a recent version of Django. If this file doesn’t exist, you’ll need to create
it. See the How to deploy with WSGI documentation for the default
contents you should put in this file and what else you can add to it.
The Django-specific options here are:
chdir: The path to the directory that needs to be on Python’s import path – i.e., the directory containing the
module: The WSGI module to use – probably the
env: Should probably contain at least
home: Optional path to your project virtualenv.
Example ini configuration file:
Example ini configuration file usage:
uwsgi --ini uwsgi.ini
UnicodeEncodeError for file uploads
If you get a
UnicodeEncodeError when uploading files with file names
that contain non-ASCII characters, make sure uWSGI is configured to accept
non-ASCII file names by adding this to your
env = LANG=en_US.UTF-8
See the Files section of the Unicode reference guide for details.
See the uWSGI docs on managing the uWSGI process for information on starting, stopping and reloading the uWSGI workers.