Taming the Kraken - How Operations enables developer productivity
summary
CustomInk moves from bi-weekly, risky deploys to small, single-change releases by running ~20–25 Rails apps, handling 40M app requests/week, and enforcing per-branch staging with disposable servers provisioned by Chef. Local devs boot environments with Vagrant + Chef and run branch builds in Jenkins via Capistrano hooks; a visible Green Screen shows build health. Deploys go one-at-a-time from a capHub central repo, developers deploy their own merges, rollback becomes rare, and cycle time drops from days to minutes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:12Old deployment problems
- 6:21Deploy early and often
- 9:59Automating with Chef
- 11:47Simplifying development with Vagrant
- 13:14Branch testing with Jenkins
- 15:41Managing prod apps
- 17:27Cap Hub deployments
- 18:48Campfire queue
- 20:10New deployment benefits
- 22:51How to get started with these changes
- 26:06Q&A
related talks
36mContinuous Deployment with Rails
24mContinuous Deployment at Scale
34mGuide to Continuous Deployment with Rails
46mContinuous Deployment Workflows
30mKeith and Mario's Guide to Continuous Deployment with Rails
11mWorking with sharp tools - A case study of Continuous deployment
30mRelease Early and Release Often: Reducing deployment friction
35mTaming a beast