Guide to Continuous Deployment with Rails
summary
Argues for automatically deploying master on green CI and shows the exact stack and habits: RuboCop and Kane checks, Travis/Buildbox CI, Capybara smoke tests, Rollout feature flags, BugSnag/NewRelic monitoring and PagerDuty. Demonstrates turning the merge pull request button into a deploy button, handling zero downtime migrations with a two‑deploy pattern and dirty ActiveRecord hacks, and rolling features out to developers then all users. Reports teams doing 4.7 deploys per day versus 1.9 and a working social‑buttons rollout on a Rails app deployed to Heroku.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:12WHY CONTINUOUS DEPLOYMENT?
- 7:27PROCESS IS YOLO. NOT THE CODE.
- 11:39Reviewing Code GITHUB PULL REQUESTS
- 15:14Smoke Tests RUNS POST DEPLOY AGAINST REMOTE SERVER
- 15:56TESTS RUN AGAINST REMOTE SERVER & LOCAL
- 16:35Zeno Downtime Deploys DEPLOYING NEW CODE WITHOUT MAINTENANCE PAGE
- 17:46EASY WAY: MAINTENANCE PAGE
- 18:28DEPLOY CODE TO USE NEW COLUMN
- 22:35Rolling Back Deploys TURN ON MAINTENANCE PAGE
- 24:32git push heroku-staging master 8 rake smoke: staging 9 git push heroku master 10 rake smoke:production
- 29:35FIN.
related talks
36mContinuous Deployment with Rails
30mKeith and Mario's Guide to Continuous Deployment with Rails
34mStrong Practices for Rails Applications Continuous Delivery
49mRuby Software Continuously Delivered and Exhaustively Explained
42mCONTINUOUS DELIVERY FOR RUBYISTS
35mCI/CD and devops with Ruby and Rails
32mOperating Rails: what about after you deploy?
31mOperating Rails: What About After You Deploy?
