Refs #23430 -- gunicorn wants a module, not file
This commit is contained in:
parent
0e4d79c4f0
commit
fa74dba994
|
@ -22,7 +22,7 @@ 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 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
|
`application`. So for a typical Django project, invoking gunicorn would look
|
||||||
like::
|
like::
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue