"What Django Deployment is Really About"
summary
Breaks Django deployment into four concrete concerns: static files (use manage.py collectstatic, or middleware like WhiteNoise and CDNs, and serve uploads from S3 instead of local disk), database (sqlite works in dev but production often uses Postgres with host/port/credentials and requires running migrations), WSGI server (use Gunicorn, uWSGI or Waitress to run the wsgi callable), and web server/PaaS choices (nginx/Apache on a VPS vs Heroku/pythonanywhere/platforms, plus tools like django-check, django-simple-deploy, Django Production and Docker pros/cons).
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:06Why Django deployment matters
- 2:53Common challenges
- 4:16Four key concerns
- 5:19Static files and web servers
- 8:54White Noise for static files
- 10:40Media files and cloud storage
- 12:04Database differences in development vs deployment
- 14:54What is a WSGI server
- 17:03VPS versus PaaS
- 19:34VPS versus platform as a service
- 21:00Django deployment checklist
- 22:45Django Simple Deploy
- 23:46Django Production overview
- 25:10Docker in Django
- 28:20Docker limits and alternatives
- 29:02Summary
related talks
26mWhat Django Deployment is Really About
22mWhat is deployment, anyway?
41mProduction Django: Building a Highly Scalable, Secure Django Site
41mDjango Deployments Done Right
32mChoose Your Own Django Deployment Adventure
43mHosting and DevOps for Django
44mPrepping Your Project for Production
26mAutomating initial deployments with django-simple-deploy with Eric Matthes