p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #23959 -- Clarified when checks automatically run.

This commit is contained in:
Alexander Schulze 2014-12-22 02:54:42 +01:00 committed by Tim Graham
parent 994d6137a2
commit cf2390be16
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/topics/checks.txt
View File

@ -12,8 +12,9 @@ The framework is extensible so you can easily add your own checks.
Checks can be triggered explicitly via the :djadmin:`check` command. Checks are Checks can be triggered explicitly via the :djadmin:`check` command. Checks are
triggered implicitly before most commands, including :djadmin:`runserver` and triggered implicitly before most commands, including :djadmin:`runserver` and
:djadmin:`migrate`. For performance reasons, the checks are not performed if :djadmin:`migrate`. For performance reasons, checks are not run as part of the
:setting:`DEBUG` is set to ``False``. WSGI stack that is used in deployment. If you need to run system checks on your
deployment server, trigger them explicitly using :djadmin:`check`.
Serious errors will prevent Django commands (such as :djadmin:`runserver`) from Serious errors will prevent Django commands (such as :djadmin:`runserver`) from
running at all. Minor problems are reported to the console. If you have inspected running at all. Minor problems are reported to the console. If you have inspected