mirror of
https://github.com/django/django.git
synced 2025-12-04 00:55:36 +00:00
Fixed #23868 -- Added support for non-unique django-admin-options in docs.
Also documented missing short command line options to fix #24134. This bumps the minimum sphinx version required to build the docs to 1.3.4. Thanks Simon Charette for review.
This commit is contained in:
parent
fd1c5bb041
commit
e519aab43a
31 changed files with 543 additions and 616 deletions
|
|
@ -123,8 +123,8 @@ parameter of the handle method. See the :py:mod:`argparse` Python documentation
|
|||
for more about ``add_argument`` usage.
|
||||
|
||||
In addition to being able to add custom command line options, all
|
||||
:doc:`management commands</ref/django-admin>` can accept some
|
||||
default options such as :djadminopt:`--verbosity` and :djadminopt:`--traceback`.
|
||||
:doc:`management commands</ref/django-admin>` can accept some default options
|
||||
such as :option:`--verbosity` and :option:`--traceback`.
|
||||
|
||||
.. _management-commands-and-locales:
|
||||
|
||||
|
|
@ -267,9 +267,8 @@ All attributes can be set in your derived class and can be used in
|
|||
see the available styles (use uppercased versions of the "roles" described
|
||||
in that section).
|
||||
|
||||
If you pass the :djadminopt:`--no-color` option when running your
|
||||
command, all ``self.style()`` calls will return the original string
|
||||
uncolored.
|
||||
If you pass the :option:`--no-color` option when running your command, all
|
||||
``self.style()`` calls will return the original string uncolored.
|
||||
|
||||
Methods
|
||||
-------
|
||||
|
|
|
|||
|
|
@ -32,10 +32,9 @@ module for production.
|
|||
Run ``manage.py check --deploy``
|
||||
================================
|
||||
|
||||
Some of the checks described below can be automated using the
|
||||
:djadminopt:`--deploy` option of the :djadmin:`check` command. Be sure to run it
|
||||
against your production settings file as described in the option's
|
||||
documentation.
|
||||
Some of the checks described below can be automated using the :option:`check
|
||||
--deploy` option. Be sure to run it against your production settings file as
|
||||
described in the option's documentation.
|
||||
|
||||
Critical settings
|
||||
=================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue