summaryrefslogtreecommitdiff
path: root/docs/howto/deployment/modwsgi.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/howto/deployment/modwsgi.txt')
-rw-r--r--docs/howto/deployment/modwsgi.txt27
1 files changed, 25 insertions, 2 deletions
diff --git a/docs/howto/deployment/modwsgi.txt b/docs/howto/deployment/modwsgi.txt
index 12de53f53d..e873006af0 100644
--- a/docs/howto/deployment/modwsgi.txt
+++ b/docs/howto/deployment/modwsgi.txt
@@ -1,5 +1,3 @@
-.. _howto-deployment-modwsgi:
-
==========================================
How to use Django with Apache and mod_wsgi
==========================================
@@ -55,6 +53,8 @@ just above the final ``import`` line to place your project on the path. Remember
replace 'mysite.settings' with your correct settings file, and '/usr/local/django'
with your own project's location.
+.. _serving-media-files:
+
Serving media files
===================
@@ -108,6 +108,29 @@ in the mod_wsgi documentation on `hosting static files`_.
.. _hosting static files: http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines#Hosting_Of_Static_Files
+.. _serving-the-admin-files:
+
+Serving the admin files
+=======================
+
+Note that the Django development server automagically serves admin media files,
+but this is not the case when you use any other server arrangement. You're
+responsible for setting up Apache, or whichever media server you're using, to
+serve the admin files.
+
+The admin files live in (:file:`django/contrib/admin/media`) of the Django
+distribution.
+
+Here are two recommended approaches:
+
+ 1. Create a symbolic link to the admin media files from within your
+ document root. This way, all of your Django-related files -- code **and**
+ templates -- stay in one place, and you'll still be able to ``svn
+ update`` your code to get the latest admin templates, if they change.
+
+ 2. Or, copy the admin media files so that they live within your Apache
+ document root.
+
Details
=======