Fixed #18306 -- Removed most of GeoDjango-specific deployment docs

1 files changed, 6 insertions, 53 deletions

diff --git a/docs/ref/contrib/gis/deployment.txt b/docs/ref/contrib/gis/deployment.txt
index d98fc51837..f90c9c2e91 100644
--- a/docs/ref/contrib/gis/deployment.txt
+++ b/docs/ref/contrib/gis/deployment.txt
@@ -2,6 +2,10 @@
 Deploying GeoDjango
 ===================
 
+Basically, the deployment of a GeoDjango application is not different from
+the deployment of a normal Django application. Please consult Django's
+:doc:`deployment documentation </howto/deployment/index>`.
+
 .. warning::
 
     GeoDjango uses the GDAL geospatial library which is
@@ -10,58 +14,7 @@ Deploying GeoDjango
     appropriate configuration of Apache or the prefork method
     when using FastCGI through another Web server.
 
-Apache
-======
-In this section there are some example ``VirtualHost`` directives for
-when deploying using ``mod_wsgi``, which is now officially the recommended
-way to deploy Django applications with Apache.
-As long as ``mod_wsgi`` is configured correctly, it does not
-matter whether the version of Apache is prefork or worker.
-
-.. note::
-
-    The ``Alias`` and ``Directory`` configurations in the examples
-    below use an example path to a system-wide installation folder of Django.
-    Substitute in an appropriate location, if necessary, as it may be
-    different than the path on your system.
-
-``mod_wsgi``
-------------
-
-Example::
-
-    <VirtualHost *:80>
-      WSGIDaemonProcess geodjango user=geo group=geo processes=5 threads=1
-      WSGIProcessGroup geodjango
-      WSGIScriptAlias / /home/geo/geodjango/world.wsgi
-
-      Alias /media/ "/usr/lib/python2.6/site-packages/django/contrib/admin/media/"
-      <Directory "/usr/lib/python2.6/site-packages/django/contrib/admin/media/">
-        Order allow,deny
-        Options Indexes
-        Allow from all
-        IndexOptions FancyIndexing
-      </Directory>
-
-    </VirtualHost>
-
-.. warning::
-
-    If the ``WSGIDaemonProcess`` attribute ``threads`` is not set to ``1``, then
+    For example, when configuring your application with ``mod_wsgi``,
+    set the ``WSGIDaemonProcess`` attribute ``threads`` to ``1``, unless
     Apache may crash when running your GeoDjango application.  Increase the
     number of ``processes`` instead.
-
-For more information, please consult Django's
-:doc:`mod_wsgi documentation </howto/deployment/wsgi/modwsgi>`.
-
-Lighttpd
-========
-
-FastCGI
--------
-
-Nginx
-=====
-
-FastCGI
--------