Containerless Django: Deploying without Docker
summary
Claims a full Docker-free pipeline that actually builds a runnable .pyz artifact using shiv pyz bundle, installs dependencies with pip-m lockfile determinism, runs collectstatic and tests against the exact artifact, and deploys by downloading a single file. Uses pyuwizki/uwsgi for serving and systemd flags for sandboxing and quick rollbacks. Notes tradeoffs: requires Python on host, less isolation than containers, but yields much smaller artifacts (hundreds of MB vs gigabytes) and suits under ~50 services.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:46Docker Has Its Drawbacks
- 7:36What Is the Ideal Deployment
- 13:45Make Sure Your Django Project Is a Proper Python Package
- 15:03Templates and Static Files
- 15:15Static Files and Templates
- 15:39Production Web Server
- 16:56Django Piusky
- 20:29Configuration
- 21:44Goodconf
- 27:21Capability Bounding Set
- 28:41Rolling Deployments
- 31:35Pros and Cons to this Approach
- 34:44Docker Is Not for Everybody
related talks
29mCan packaging improve Django deployments?
41mDjango Deployments Done Right
26mWhat Django Deployment is Really About
30m"What Django Deployment is Really About"
28mScaling Down: Running Large Sites Locally
34mContinuous Deployment for webapps based on Django
34mAn Intro to Docker for Djangonauts
53mDjango productivity tips and tricks