test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #23430 -- simplified gunicorn deployment docs.

This commit is contained in:
Collin Anderson 2014-09-05 16:41:47 -07:00 committed by Tim Graham
parent f7d3a6255c
commit 77b3907d6d
1 changed files with 7 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/howto/deployment/wsgi/gunicorn.txt
View File

@ -22,21 +22,15 @@ Running Django in Gunicorn as a generic WSGI application
When Gunicorn is installed, a ``gunicorn`` command is available which starts When Gunicorn is installed, a ``gunicorn`` command is available which starts
the Gunicorn server process. At its simplest, gunicorn just needs to be called the Gunicorn server process. At its simplest, gunicorn just needs to be called
with the location of a WSGI application object.:: with the location of a file containing a WSGI application object named
`application`. So for a typical Django project, invoking gunicorn would look
like::
gunicorn [OPTIONS] APP_MODULE gunicorn myproject.wsgi
Where ``APP_MODULE`` is of the pattern ``MODULE_NAME:VARIABLE_NAME``. The This will start one process running one thread listening on ``127.0.0.1:8000``.
module name should be a full dotted path. The variable name refers to a WSGI It requires that your project be on the Python path; the simplest way to ensure
callable that should be found in the specified module. that is to run this command from the same directory as your ``manage.py`` file.
So for a typical Django project, invoking gunicorn would look like::
gunicorn myproject.wsgi:application
(This requires that your project be on the Python path; the simplest way to
ensure that is to run this command from the same directory as your
``manage.py`` file.)
See Gunicorn's `deployment documentation`_ for additional tips. See Gunicorn's `deployment documentation`_ for additional tips.