  .sp
  Or you could run it directly on a production or staging deployment to verify
  that the correct settings are in use (omitting \fB\-\-settings\fP). You could even
  make it part of your integration test suite.
  .SS compilemessages
  .INDENT 0.0
  .TP
  .B django\-admin compilemessages
  .UNINDENT
  .sp
 
</s> remove 
.sp
The \fB\-\-deploy\fP option activates some additional checks that are only relevant
in a deployment setting.
 </s> add Activates some additional checks that are only relevant in a deployment setting. </s> remove 
.sp
The \fB\-\-keepdb\fP option can be used to preserve the test database between test
runs. This has the advantage of skipping both the create and destroy actions
which can greatly decrease the time to run tests, especially those in a large
test suite. If the test database does not exist, it will be created on the first
run and then preserved for each subsequent run. Any unapplied migrations will also
be applied to the test database before running the test suite.
 </s> add Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite. </s> remove The \fB\-\-dry\-run\fP option was added.

.SS dbshell
 </s> add Prints the SQL that would be run without actually running it, so you can
customize it or use the migrations framework.
.SS \fBdbshell\fP </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 .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 
.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
  .sp
  Or you could run it directly on a production or staging deployment to verify
  that the correct settings are in use (omitting \fB\-\-settings\fP). You could even
  make it part of your integration test suite.
.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
  .INDENT 0.0
  .TP
  .B django\-admin compilemessages
  .UNINDENT
  .sp
keep keep keep keep replace keep keep keep keep keep
 Updated man page for Django 2.0 alpha. 
docs/man/django-admin.1