mirror of
https://github.com/django/django.git
synced 2025-10-23 21:59:11 +00:00
Fixed some ReST errors regarding backticks
This commit is contained in:
@@ -28,6 +28,7 @@ the easiest, fastest, and most stable deployment choice.
|
||||
* `Chapter 12 of the Django Book (second edition)`_ discusses deployment
|
||||
and especially scaling in more detail. However, note that this edition
|
||||
was written against Django version 1.1 and has not been updated since
|
||||
`mod_python` was first deprecated, then completely removed in Django 1.5.
|
||||
``mod_python`` was first deprecated, then completely removed in
|
||||
Django 1.5.
|
||||
|
||||
.. _chapter 12 of the django book (second edition): http://djangobook.com/en/2.0/chapter12/
|
||||
|
||||
@@ -16,7 +16,7 @@ version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
|
||||
|
||||
.. note::
|
||||
If you have installed a :ref:`custom User model <auth-custom-user>` and
|
||||
want to use this default auth handler, it must support an `is_active`
|
||||
want to use this default auth handler, it must support an ``is_active``
|
||||
attribute. If you want to use group based authorization, your custom user
|
||||
must have a relation named 'groups', referring to a related object that has
|
||||
a 'name' field. You can also specify your own custom mod_wsgi
|
||||
|
||||
@@ -193,7 +193,7 @@ other approaches:
|
||||
configuration).
|
||||
|
||||
2. Use an ``Alias`` directive, as demonstrated above, to alias the appropriate
|
||||
URL (probably :setting:`STATIC_URL` + `admin/`) to the actual location of
|
||||
URL (probably :setting:`STATIC_URL` + ``admin/``) to the actual location of
|
||||
the admin files.
|
||||
|
||||
3. Copy the admin static files so that they live within your Apache
|
||||
|
||||
Reference in New Issue
Block a user