What is deployment, anyway?
summary
A clear checklist: deployment means copying code, running a production web server, migrating a real database and serving static assets — not using the development helpers. Concrete tools and commands matter: WSGI with Gunicorn or uWSGI, manage.py makemigrations migrate and collectstatic, Postgres or a managed DB rather than SQLite in production. The local runserver and built‑in static serving work for development but are explicitly unsuitable for production.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:24What is deployment
- 0:34points of interest out of the box django complexities helpers
- 0:50django 3.0.5 python 3.8.2
- 2:52django good local development story
- 3:42We're in the business of making Web frameworks, not Web servers
- 4:14What is production, anyway?
- 4:51What is a web server, anyway?
- 5:21What is "static", anyway?
- 7:48state
- 8:44"Every production setup will be a bit different" - django documentation
- 8:56"It depends." - every deployment talk ever
- 10:29WSGI Web Server Gateway Interface
- 11:20Deploy a django app with a WSGI Webserver
- 11:35How do you deploy WSGI webserver?
- 12:09infrastructure management
- 13:22Other options: Custom hardware Functions as a Service
- 17:13What do you want to worry about?
- 19:26to deploy django: fun djange connect to a database serve static files
- 20:54What is django deployment, anyway?
- 21:19The reason there's no one answer.
related talks
26mWhat Django Deployment is Really About
30m"What Django Deployment is Really About"
41mDjango Deployments Done Right
44mHow to Write Deployment-friendly Applications
26mProtoype for Production
29mCan packaging improve Django deployments?
32mContinuous Deployment and Release of Django Apps
34mContinuous Deployment for webapps based on Django