Django is full of shortcuts to make web developers” lives easier, but all\nthose tools are of no use if you can’t easily deploy your sites. Since Django’s\ninception, ease of deployment has been a major goal.
\nThere are many options for deploying your Django application, based on your\narchitecture or your particular business needs, but that discussion is outside\nthe scope of what Django can give you as guidance.
\nDjango, being a web framework, needs a web server in order to operate. And\nsince most web servers don’t natively speak Python, we need an interface to\nmake that communication happen. The runserver command starts a\nlightweight development server, which is not suitable for production.
Django currently supports two interfaces: WSGI and ASGI.
\nWSGI is the main Python standard for communicating between web servers and\napplications, but it only supports synchronous code.
ASGI is the new, asynchronous-friendly standard that will allow your\nDjango site to use asynchronous Python features, and asynchronous Django\nfeatures as they are developed.
You should also consider how you will handle static files for your application, and how to handle\nerror reporting.
\nFinally, before you deploy your application to production, you should run\nthrough our deployment checklist to ensure that your\nconfigurations are suitable.
\n