  .TP
  .B \-\-deploy
  .UNINDENT
  .sp
  
  .sp
  The \fB\-\-deploy\fP option activates some additional checks that are only relevant
  in a deployment setting.
  .sp
  You can use this option in your local development environment, but since your
  local development settings module may not have many of your production settings,
  you will probably want to point the \fBcheck\fP command at a different settings
  module, either by setting the \fBDJANGO_SETTINGS_MODULE\fP environment variable,
 
</s> remove information from your settings file. See \fB/topics/cache\fP for more
 </s> add information from your settings file. See /topics/cache for more </s> remove .SS compilemessages
 </s> add .INDENT 0.0
.TP
.B \-\-fail\-level {CRITICAL,ERROR,WARNING,INFO,DEBUG}
.UNINDENT
.sp
Specifies the message level that will cause the command to exit with a non\-zero
status. Default is \fBERROR\fP\&.
.SS \fBcompilemessages\fP </s> remove .sp
Explicitly specifies the settings module to use. The settings module should be
in Python package syntax, e.g. \fBmysite.settings\fP\&. If this isn\(aqt provided,
\fBdjango\-admin\fP will use the \fBDJANGO_SETTINGS_MODULE\fP environment
variable.
.sp
Note that this option is unnecessary in \fBmanage.py\fP, because it uses
\fBsettings.py\fP from the current project by default.
 </s> add  </s> remove The \fI\%\-\-database\fP option can be used to specify the database
onto which the cache table will be installed, but since this information is
pulled from your settings by default, it\(aqs typically not needed.
.sp
The \fI\%\-\-dry\-run\fP option will print the SQL that would be run without
actually running it, so you can customize it or use the migrations framework.
 </s> add Specifies the database in which the cache table(s) will be created. Defaults to
\fBdefault\fP\&.
.INDENT 0.0
.TP
.B \-\-dry\-run
.UNINDENT </s> remove The \fBsystem check framework\fP performs many different
types of checks. These check types are categorized with tags. You can use these tags
to restrict the checks performed to just those in a particular category. For example,
to perform only security and compatibility checks, you would run:
 </s> add The system check framework performs many different types of checks that are
categorized with tags\&. You can use these
tags to restrict the checks performed to just those in a particular category.
For example, to perform only models and compatibility checks, run:
Activates some additional checks that are only relevant in a deployment setting.
  .TP
  .B \-\-deploy
  .UNINDENT
  .sp
Activates some additional checks that are only relevant in a deployment setting.
Activates some additional checks that are only relevant in a deployment setting.
Activates some additional checks that are only relevant in a deployment setting.
Activates some additional checks that are only relevant in a deployment setting.
  .sp
  You can use this option in your local development environment, but since your
  local development settings module may not have many of your production settings,
  you will probably want to point the \fBcheck\fP command at a different settings
  module, either by setting the \fBDJANGO_SETTINGS_MODULE\fP environment variable,
keep keep keep keep replace replace replace replace keep keep keep keep keep
 Updated man page for Django 2.0 alpha. 
docs/man/django-admin.1