Edited deployment doc changes from [17338]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17421 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ead8a869ce
commit
442ab475c8
|
@ -299,7 +299,7 @@ Django distribution.
|
|||
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
|
||||
your Web server 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
|
||||
|
|
|
@ -162,7 +162,7 @@ Django distribution.
|
|||
We **strongly** recommend using :mod:`django.contrib.staticfiles` to handle the
|
||||
admin files (along with a Web server as outlined in the previous section; this
|
||||
means using the :djadmin:`collectstatic` management command to collect the
|
||||
static files in :setting:`STATIC_ROOT`, and then configuring your webserver to
|
||||
static files in :setting:`STATIC_ROOT`, and then configuring your Web server to
|
||||
serve :setting:`STATIC_ROOT` at :setting:`STATIC_URL`), but here are three
|
||||
other approaches:
|
||||
|
||||
|
|
Loading…
Reference in New Issue