Skip to content

Commit

Permalink
Fixed #19633 - Discouraged use of gunicorn's Django integration.
Browse files Browse the repository at this point in the history
  • Loading branch information
@timgraham
timgraham committed Jan 23, 2013
1 parent 214fb70 commit 0db8627
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions docs/howto/deployment/wsgi/gunicorn.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,12 @@ ensure that is to run this command from the same directory as your
Using Gunicorn's Django integration
===================================

.. note::

If you are using Django 1.4 or newer, it’s highly recommended to simply run
your application with the WSGI interface using the ``gunicorn`` command
as described above.

This comment has been minimized.

Sign in to view

Copy link
@typeshige

typeshige Jan 23, 2013

For the curious, it would be helpful if it stated briefly why this is recommended.

This comment has been minimized.

Sign in to view

Copy link
@kitsunde

kitsunde Jan 24, 2013

@typeshige It seems like the recommendation originates from gunicorn. https://gunicorn-docs.readthedocs.org/en/latest/run.html?highlight=django#gunicorn-django I'm not sure why, either.

This comment has been minimized.

Sign in to view

Copy link
@mjtamlyn

mjtamlyn Jan 24, 2013

Member

It's to do with the fact Django is now WSGI compliant so gunicorn is wrapping Django's own WSGI rather than hacking around inside django as it used to need to. I think it rather substantially reduces the amount of code on both sides.

This comment has been minimized.

Sign in to view

Copy link
@kitsunde

kitsunde Jan 24, 2013

@mjtamlyn I see, thank you.
To use Gunicorn's built-in Django integration, first add ``"gunicorn"`` to
:setting:`INSTALLED_APPS`. Then run ``python manage.py run_gunicorn``.

Expand Down

0 comments on commit 0db8627

Please sign in to comment.