From a948277bea4af819a63ad69402712c4e8bde9203 Mon Sep 17 00:00:00 2001
From: Alexander Schulze <alexander.schulze@gmail.com>
Date: Mon, 22 Dec 2014 02:21:10 +0100
Subject: [PATCH] documentation correction for ticket #23959
---
docs/topics/checks.txt | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt
index b40b06f..76ec134 100644
a
|
b
|
The framework is extensible so you can easily add your own checks.
|
12 | 12 | |
13 | 13 | Checks can be triggered explicitly via the :djadmin:`check` command. Checks are |
14 | 14 | triggered implicitly before most commands, including :djadmin:`runserver` and |
15 | | :djadmin:`migrate`. For performance reasons, the checks are not performed if |
16 | | :setting:`DEBUG` is set to ``False``. |
| 15 | :djadmin:`migrate`. |
| 16 | |
| 17 | .. warning:: |
| 18 | |
| 19 | For performance reasons, the checks are not performed in the deployed version |
| 20 | of Django. If you need to run system checks on your deployment server, you |
| 21 | need to trigger them explicitly via :djadmin:`check`. |
17 | 22 | |
18 | 23 | Serious errors will prevent Django commands (such as :djadmin:`runserver`) from |
19 | 24 | running at all. Minor problems are reported to the console. If you have inspected |