Production Django: Building a Highly Scalable, Secure Django Site
summary
Shows concrete operational choices and tools: aim for a single repeatable deployment step (force master checkout via Fabric), prefer scheduled pushes for organizational coordination, and restrict root access while keeping sensitive data off web servers and using store secrets in environment variables managed by Puppet. Recommend local dev that mirrors prod with Vagrant, and a basic scale plan of load balancer + two app servers to allow hot swaps. Debug and monitoring stack includes Django Debug Toolbar, New Relic, Sentry, Supervisor and Flower.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:02Our Agenda
- 3:41Deploy: What Most of Us Do
- 6:08Deploy: Recommendations
- 9:10Secure: What Most of Us Do
- 10:09Secure: Recommendations
- 15:23Segment: What Most of Us Do
- 16:26Segment: Recommendations
- 18:29Scale: What Most of Us Do
- 19:18Scale: Recommendations
- 20:19Gotchas
- 22:42Out of control queries
- 24:14Tools
- 24:27Django Debug Toolbar
- 26:16New Relic
- 27:32Supervisor
- 28:52Flower
related talks
53mDjango productivity tips and tricks
30m"What Django Deployment is Really About"
53mDjango productivity tips and tricks
26mProtoype for Production
32mChoose Your Own Django Deployment Adventure
34mContinuous Deployment for webapps based on Django
01h 06mEffective Django
44mPrepping Your Project for Production