update doc for django and paster integration

gunicorn_django and gunicorn_paster commands are now deprecated so
remove them from the doc. While I am here, update the integration doc.

docs/source/run.rst

@@ -49,81 +49,52 @@ Example with test app::
 
     $ gunicorn --workers=2 test:app
 
-gunicorn_django
----------------
-
-You might not have guessed it, but this script is used to serve Django
-applications. Basic usage::
-
-    $ gunicorn_django [OPTIONS] [SETTINGS_PATH]
-
-By default ``SETTINGS_PATH`` will look for ``settings.py`` in the current
-directory.
-
-Example with your Django project::
-
-    $ cd path/to/yourdjangoproject
-    $ gunicorn_django --workers=2
-
-.. note:: If you run Django 1.4 or newer, it's highly recommended to
-    simply run your application with the `WSGI interface
-    <https://docs.djangoproject.com/en/1.4/howto/deployment/wsgi/>`_ using
-    the `gunicorn`_ command.
-
-gunicorn_paster
----------------
-
-Yeah, for Paster-compatible frameworks (Pylons, TurboGears 2, ...). We
-apologize for the lack of script name creativity. And some usage::
-
-    $ gunicorn_paster [OPTIONS] paste_config.ini
-
-Simple example::
-
-    $ cd yourpasteproject
-    $ gunicorn_paster --workers=2 development.ini
 
 Integration
 ===========
 
-Alternatively, we also provide integration for both Django and Paster
+We also provide integration for both Django and Paster applications.
-applications in case your deployment strategy would be better served by such
-invocation styles.
 
-Django ./manage.py
+Django
-------------------
+------
 
-You can add a ``run_gunicorn`` command to your ``./manage.py`` simply by adding
+gunicorn just needs to be called with a the location of a WSGI
-gunicorn to your ``INSTALLED_APPS``::
+application object.:
 
-    INSTALLED_APPS = (
+    gunicorn [OPTIONS] APP_MODULE
-        ...
+
-        "gunicorn",
+Where APP_MODULE is of the pattern MODULE_NAME:VARIABLE_NAME. The module
-    )
+name should be a full dotted path. The variable name refers to a WSGI
+callable that should be found in the specified module.
+
+So for a typical Django project, invoking gunicorn would look like:
+
+    gunicorn myproject.wsgi:application
+
+(This requires that your project be on the Python path; the simplest way
+to ensure that is to run this command from the same directory as your
+manage.py file.)
+
+You can use the
+[--env](http://docs.gunicorn.org/en/latest/settings.html#raw-env) option
+to set the path to load the settings. In case you need it you can also
+add your application path to PYTHONPATH using the
+[--pythonpath](http://docs.gunicorn.org/en/latest/settings.html#pythonpath)
+option.
 
-Then you can run::
 
-    python manage.py run_gunicorn
 
 paster serve
 ------------
 
-If you're wanting to keep on keeping on with the usual paster serve command,
+If you are a user/developer of a paste-compatible framework/app (as
-you can specify the Gunicorn server settings in your configuration file::
+Pyramid, Pylons and Turbogears) you can use the gunicorn
+[--paste](http://docs.gunicorn.org/en/latest/settings.html#paste) option
+to run your application.
 
-    [server:main]
+For example:
-    use = egg:gunicorn#main
-    host = 127.0.0.1
-    port = 5000
-    # Uncomment the line below to use other advanced gunicorn settings
-    #config = %(here)/gunicorn.conf.py
 
-And then as per usual::
+    gunicorn --paste development.ini -b :8080 --chdir /path/to/project
 
-    $ cd yourpasteproject
+It is all here. No configuration files nor additional python modules to
-    $ paster serve development.ini workers=2
+write !!
-
-However, in this configuration, Gunicorn does not reload the application when
-new workers are started. See the note about preloading_.
-
-.. _preloading: configure.html#preload-app