mirror of
https://github.com/django/django.git
synced 2025-08-08 12:58:37 +00:00
[5.1.x] Refs #35591 -- Emphasized that runserver is not suitable for production.
Backport of cec62fb99e
from main.
This commit is contained in:
parent
291fa5fbbe
commit
73fcb14cd8
3 changed files with 15 additions and 6 deletions
|
@ -36,6 +36,14 @@ Some of the checks described below can be automated using the :option:`check
|
|||
--deploy` option. Be sure to run it against your production settings file as
|
||||
described in the option's documentation.
|
||||
|
||||
Switch away from ``manage.py runserver``
|
||||
========================================
|
||||
|
||||
The :djadmin:`runserver` command is not designed for a production setting. Be
|
||||
sure to switch to a production-ready WSGI or ASGI server. For a few common
|
||||
options, see :doc:`WSGI servers </howto/deployment/wsgi/index>` or
|
||||
:doc:`ASGI servers </howto/deployment/asgi/index>`.
|
||||
|
||||
Critical settings
|
||||
=================
|
||||
|
||||
|
|
|
@ -12,7 +12,8 @@ the scope of what Django can give you as guidance.
|
|||
|
||||
Django, being a web framework, needs a web server in order to operate. And
|
||||
since most web servers don't natively speak Python, we need an interface to
|
||||
make that communication happen.
|
||||
make that communication happen. The :djadmin:`runserver` command starts a
|
||||
lightweight development server, which is not suitable for production.
|
||||
|
||||
Django currently supports two interfaces: WSGI and ASGI.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue