From fa74dba994bb3e70839623073a6ab5dfc815a9b3 Mon Sep 17 00:00:00 2001 From: Collin Anderson Date: Sat, 6 Sep 2014 08:13:45 -0700 Subject: [PATCH] Refs #23430 -- gunicorn wants a module, not file --- docs/howto/deployment/wsgi/gunicorn.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/deployment/wsgi/gunicorn.txt b/docs/howto/deployment/wsgi/gunicorn.txt index 0e50ac66b38..c5c5ba9e22c 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::