diff options
| author | Collin Anderson <cmawebsite@gmail.com> | 2014-09-06 08:13:45 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-09-06 12:21:36 -0400 |
| commit | ba8983333a561b56c44c2d72c87f918604eae7f9 (patch) | |
| tree | c329eb6bf424cbd58390f5c5a98a1f93f98c6c4b | |
| parent | a932c596fc5bfcfcb358981540917c8d6f9dc575 (diff) | |
[1.7.x] Refs #23430 -- gunicorn wants a module, not file
Backport of fa74dba994 from master
| -rw-r--r-- | docs/howto/deployment/wsgi/gunicorn.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/deployment/wsgi/gunicorn.txt b/docs/howto/deployment/wsgi/gunicorn.txt index 0e50ac66b3..c5c5ba9e22 100644 --- a/docs/howto/deployment/wsgi/gunicorn.txt +++ b/docs/howto/deployment/wsgi/gunicorn.txt @@ -22,7 +22,7 @@ Running Django in Gunicorn as a generic WSGI application When Gunicorn is installed, a ``gunicorn`` command is available which starts the Gunicorn server process. At its simplest, gunicorn just needs to be called -with the location of a file containing a WSGI application object named +with the location of a module containing a WSGI application object named `application`. So for a typical Django project, invoking gunicorn would look like:: |