From 8e9043bccbe18d4b6d1550bffeff4c28e5135f6c Mon Sep 17 00:00:00 2001 From: Carl Meyer Date: Wed, 4 Jan 2012 18:08:13 +0000 Subject: Clarified deployment docs to avoid giving users the impression that staticfiles should be used to actually serve files in production. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17338 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/deployment/modpython.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'docs/howto/deployment/modpython.txt') diff --git a/docs/howto/deployment/modpython.txt b/docs/howto/deployment/modpython.txt index 952cb3247b..fe1cd79c3a 100644 --- a/docs/howto/deployment/modpython.txt +++ b/docs/howto/deployment/modpython.txt @@ -296,8 +296,11 @@ server you're using, to serve the admin files. The admin files live in (:file:`django/contrib/admin/static/admin`) of the Django distribution. -We **strongly** recommend using :mod:`django.contrib.staticfiles` to handle -the admin files, but here are two other approaches: +We **strongly** recommend using :mod:`django.contrib.staticfiles` to handle the +admin files (this means using the :djadmin:`collectstatic` management command +to collect the static files in :setting:`STATIC_ROOT`, and then configuring +your webserver to serve :setting:`STATIC_ROOT` at :setting:`STATIC_URL`), but +here are two other approaches: 1. Create a symbolic link to the admin static files from within your document root. -- cgit v1.3