diff options
| author | Alexander Schulze <alexander.schulze@gmail.com> | 2014-12-22 02:54:42 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-12-22 11:35:19 -0500 |
| commit | cf2390be164bcb3c5670f73b0a7062d6141f8664 (patch) | |
| tree | aeda25faa1d0a2e694c89ecce31761558f8d85ff /docs | |
| parent | 994d6137a2519436d17d5b3d16cb49a3fa79f93e (diff) | |
Fixed #23959 -- Clarified when checks automatically run.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/checks.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt index b40b06f137..56bb6dfc07 100644 --- a/docs/topics/checks.txt +++ b/docs/topics/checks.txt @@ -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 triggered implicitly before most commands, including :djadmin:`runserver` and -:djadmin:`migrate`. For performance reasons, the checks are not performed if -:setting:`DEBUG` is set to ``False``. +:djadmin:`migrate`. For performance reasons, checks are not run as part of the +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 running at all. Minor problems are reported to the console. If you have inspected |