Keith and Mario's Guide to Continuous Deployment with Rails
summary
Claims that teams push master automatically on green for fast feedback and predictable deploys, using Buildbox CI + GitHub PRs, static analysis with Cane and RuboCop, feature services like Rollout/CanFlip, smoke tests against staging, Bugsnag/NewRelic/PagerDuty for monitoring, and LHM-style tools for safe migrations. They report about five deploys per day versus <2 on manual projects, show zero‑downtime techniques, prefer roll forward not rollback, and prove the workflow on Envato Studio and Desktoppr with higher confidence and fewer human errors.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 0:51Mario
- 1:49Keith
- 2:51Australia
- 3:19Melbourne
- 3:42Perth
- 4:02Bob Hawke
- 4:28Chief of Police
- 4:54Titanic II
- 6:04Continuous Deployment
- 8:00Venn Diagram
- 8:36Future Planning
- 10:57Feature Toggles
- 13:08Smoke Tests
- 14:21Zero Downtime
- 15:45Database Migrations
- 17:00Account for Migrations
- 18:08LHM
- 18:35Shit happens
- 19:25Roll back
- 20:35Application monitoring
- 21:25Business metrics
- 21:56Mixing everything together
- 24:55How to apply it
- 25:07Social Buttons
- 25:18Social Buttons Demo
- 25:33Push to GitHub
- 25:51Review Pull Request
- 26:10Merge Feature
- 26:36Deployment to Production
- 27:22Recap
- 28:40Comparison
- 29:29Conclusion
related talks
34mGuide to Continuous Deployment with Rails
36mContinuous Deployment with Rails
34mStrong Practices for Rails Applications Continuous Delivery
47mContinuous Delivery Warstories
49mRuby Software Continuously Delivered and Exhaustively Explained
46mContinuous Deployment Workflows
01h 12mPitfalls of Continuous Deployment
46mDevops for PHP Developers