[1.7.x] Added syntax highlighting for apache code blocks

Backport of fde4857fb83101d27ae4cb3552a6a6cf20d3d8ce from master

1 files changed, 9 insertions, 3 deletions

diff --git a/docs/howto/deployment/wsgi/modwsgi.txt b/docs/howto/deployment/wsgi/modwsgi.txt
index 042555e4ac..d994ef125f 100644
--- a/docs/howto/deployment/wsgi/modwsgi.txt
+++ b/docs/howto/deployment/wsgi/modwsgi.txt
@@ -83,7 +83,9 @@ your Python path as well. To do this, add an additional path to your
 ``WSGIPythonPath`` directive, with multiple paths separated by a colon (``:``)
 if using a UNIX-like system, or a semicolon (``;``) if using Windows. If any
 part of a directory path contains a space character, the complete argument
-string to ``WSGIPythonPath`` must be quoted::
+string to ``WSGIPythonPath`` must be quoted:
+
+.. code-block:: apache
 
     WSGIPythonPath /path/to/mysite.com:/path/to/your/venv/lib/python2.X/site-packages
 
@@ -103,7 +105,9 @@ Django instance to run in it, you will need to add appropriate
 ``WSGIDaemonProcess`` and ``WSGIProcessGroup`` directives. A further change
 required to the above configuration if you use daemon mode is that you can't
 use ``WSGIPythonPath``; instead you should use the ``python-path`` option to
-``WSGIDaemonProcess``, for example::
+``WSGIDaemonProcess``, for example:
+
+.. code-block:: apache
 
     WSGIDaemonProcess example.com python-path=/path/to/mysite.com:/path/to/venv/lib/python2.7/site-packages
     WSGIProcessGroup example.com
@@ -137,7 +141,9 @@ static media, and others using the mod_wsgi interface to Django.
 This example sets up Django at the site root, but explicitly serves
 ``robots.txt``, ``favicon.ico``, any CSS file, and anything in the
 ``/static/`` and ``/media/`` URL space as a static file. All other URLs
-will be served using mod_wsgi::
+will be served using mod_wsgi:
+
+.. code-block:: apache
 
     Alias /robots.txt /path/to/mysite.com/static/robots.txt
     Alias /favicon.ico /path/to/mysite.com/static/favicon.ico