Continuous Deployment for webapps based on Django
summary
Claim: a Django candidate-management app moves features to production multiple times per day by automating merges, CI and deploy steps while keeping a manual tester clicks one deploy button gate. Implementation uses Git Jenkins Buildout Fabric uWSGI South, feature-branch PR testing, staging copies and DB backups. Surprising numbers: about 100 deploys with only ~5 breakages. Engineering fixes include per-instance uWSGI builds to avoid Apache/Jenkins restarts, a master FIFO to preserve PID handling, and version.txt to avoid South migration number conflicts; rollback is a scripted build-out restore.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:30Agenda
- 1:00Contest
- 1:35Price
- 2:00Sprints
- 3:05Continuous Deployment
- 4:20Our project
- 5:20Django Posterous
- 5:50Team
- 7:45Manual testing
- 8:50Tools
- 9:20Jenkins
- 11:25Jenkins plugins
- 13:15Buildout plugins
- 15:10Frontend plugins
- 15:55Fabric
- 17:00Gallery
- 18:30Rest
- 20:20Migration
- 22:30Migration on different branches
- 24:15Backups
- 25:00Monitoring
- 27:25Questions
related talks
41mDjango Deployments Done Right
32mContinuous Deployment and Release of Django Apps
01h 12mPitfalls of Continuous Deployment
36mContinuous Deployment with Rails
26mProtoype for Production
01h 12mPitfalls of Continuous Deployment
34mGuide to Continuous Deployment with Rails
41mProduction Django: Building a Highly Scalable, Secure Django Site
