Choose Your Own Django Deployment Adventure
summary
A fictional Django app called Tinder for Pets launches, uses Linode + Ubuntu for servers, Gunicorn + nginx for WSGI fronting, PostgreSQL and Celery for background work, virtualenv for isolation, and Sentry/Loggly for errors and logs. Early traffic exposes self-signed SSL, cookie sniffing, SQL injection and Heartbleed; fixes are buying CA certs, forcing HTTPS, sanitizing SQL and upgrading OpenSSL. Deploy strategy emphasizes automated config (Ansible/Chef/Puppet/Salt), CI/tests, decoupled services and zero-downtime deploys.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:21Choose Your Own Django Deployment Adventure DjangoCon 2014
- 6:46Web Server Gateway Interface
- 9:33Text "traffic" or "hackers" to (503) 946-3662 traffic
- 15:26Generate an email every time Django has an exception Use a fremium service tier like Bugsnag. Use a service like GetSentry Raven.
- 18:03Text "data" or "features" to (503) 946-3662 features
- 22:28Text "deployments" or "team" (503) 946-3662 deployments
related talks
26mWhat Django Deployment is Really About
41mProduction Django: Building a Highly Scalable, Secure Django Site
30m"What Django Deployment is Really About"
44mHow to Write Deployment-friendly Applications
41mDjango Deployments Done Right
26mProtoype for Production
34mContinuous Deployment for webapps based on Django
44mPrepping Your Project for Production