What Django Deployment is Really About
summary
Argues deployment really breaks into four concrete concerns: static files, database, WSGI server and web server, not vague recipes. Shows collectstatic and WhiteNoise for assets, recommends cloud object storage (Amazon S3) for media, warns 23% of Wagtail devs cite poor deployment docs, explains Gunicorn/Waitress/uWSGI behind nginx or Apache, contrasts VPS versus PaaS (Heroku, PythonAnywhere, fly) and demonstrates tools that work: Django Simple Deploy automates pushes to fly/platform.sh/Heroku and django-production scaffolds WhiteNoise, environment parsing, Gunicorn and health checks.
AI-written summary · about
chapters (11)
- 0:00Django deployment challenges
- 1:46Why deployment feels overwhelming
- 3:12Static files in production
- 8:52Dev versus prod databases
- 11:20WSGI server explained
- 13:29VPS versus PaaS
- 17:05Django deployment checklist
- 18:31Django Simple Deploy
- 19:35Django Production project
- 21:22Key takeaways
- 22:09Q&A on Docker and media files
related talks
30m"What Django Deployment is Really About"
41mDjango Deployments Done Right
22mWhat is deployment, anyway?
32mChoose Your Own Django Deployment Adventure
26mAutomating initial deployments with django-simple-deploy with Eric Matthes
29mCan packaging improve Django deployments?
34mContinuous Deployment for webapps based on Django
44mPrepping Your Project for Production