Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #19633 - Discouraged use of gunicorn's Django integration.

  • Loading branch information...
commit 0db86273ae1c31ee9881fe63f210cb2120fde18a 1 parent 214fb70
Tim Graham authored January 22, 2013

Showing 1 changed file with 6 additions and 0 deletions. Show diff stats Hide diff stats

  1. 6  docs/howto/deployment/wsgi/gunicorn.txt
6  docs/howto/deployment/wsgi/gunicorn.txt
@@ -48,6 +48,12 @@ ensure that is to run this command from the same directory as your
48 48
 Using Gunicorn's Django integration
49 49
 ===================================
50 50
 
  51
+.. note::
  52
+
  53
+    If you are using Django 1.4 or newer, it’s highly recommended to simply run
  54
+    your application with the WSGI interface using the ``gunicorn`` command
  55
+    as described above.
  56
+
51 57
 To use Gunicorn's built-in Django integration, first add ``"gunicorn"`` to
52 58
 :setting:`INSTALLED_APPS`. Then run ``python manage.py run_gunicorn``.
53 59
 

0 notes on commit 0db8627

Shige Abe

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

Marc Tamlyn

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.

Please sign in to comment.
Something went wrong with that request. Please try again.