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:57 -0500 |
| commit | 4c92ecd70592a7f64d8890ce2b0d67017512636a (patch) | |
| tree | 0af9e9e6cf6bbd77a2989efcff4998663db1fb48 /docs | |
| parent | 66e91543998bdece82d9c154dced1a62824e228b (diff) | |
[1.7.x] Fixed #23959 -- Clarified when checks automatically run.
Backport of cf2390be164bcb3c5670f73b0a7062d6141f8664 from master
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 076b63483d..59b8515435 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 |