~/talk

Guide to Continuous Deployment with Rails

Talkat Red Dot Ruby Conference 2014 · 2014-06-26..06-27· [devops-and-delivery]
slides:none on file

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

  1. 0:00Start
  2. 7:12WHY CONTINUOUS DEPLOYMENT?
  3. 7:27PROCESS IS YOLO. NOT THE CODE.
  4. 11:39Reviewing Code GITHUB PULL REQUESTS
  5. 15:14Smoke Tests RUNS POST DEPLOY AGAINST REMOTE SERVER
  6. 15:56TESTS RUN AGAINST REMOTE SERVER & LOCAL
  7. 16:35Zeno Downtime Deploys DEPLOYING NEW CODE WITHOUT MAINTENANCE PAGE
  8. 17:46EASY WAY: MAINTENANCE PAGE
  9. 18:28DEPLOY CODE TO USE NEW COLUMN
  10. 22:35Rolling Back Deploys TURN ON MAINTENANCE PAGE
  11. 24:32git push heroku-staging master 8 rake smoke: staging 9 git push heroku master 10 rake smoke:production
  12. 29:35FIN.
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.