Django beyond the development server.
Give a Django application an operating plan that includes the processes and state around it. A familiar admin screen does not replace production configuration or a tested deployment procedure.
Check the production configuration
Django’s deployment checklist addresses settings such as secrets, debug behavior, allowed hosts, and HTTPS. Review the checklist for the version you actually maintain. Keep secrets outside public source and make missing required configuration fail clearly.
Separate files by responsibility
Document deployable code, generated static assets, writable uploads, and private configuration. Know which process writes to each location. Avoid a release command that overwrites application data or publishes a broader directory than visitors should be able to access.
Include workers and data changes
A web response is not the entire application. Review scheduled tasks, background processes, database migrations, and their restart or retry behavior. Define which schema changes remain compatible with the previous release and which need a more careful recovery plan.