Upgrading Rails: Everyone can do it and here’s how
summary
Claim: upgrades are doable for any app because you can choose one of three concrete paths — pay someone, a long-running rails-X branch, or dual-booting. The talk gives specifics: seven Rails upgrades' worth of lessons, one upgrade that took months, a long-running branch that grew to over 400 commits, and a working bundler plug-in called boo boot that toggles versions with an env var like dependencies_next while checking sessions and signed IDs between versions.
AI-written summary · about
chapters (13)
- 0:00Rails upgrades introduction
- 2:28Traditional upgrade pain
- 4:52Why upgrade Rails
- 7:20Pre-upgrade considerations
- 10:31Three upgrade approaches
- 12:15Rails upgrade checklist
- 15:47Dual booting with Boots Boots
- 17:58Configuring Boots Boots
- 19:22Testing and CI for dual boot
- 20:04Dual boot advantages
- 21:48Dual boot cleanup
- 23:15Convincing your manager
- 24:19Closing remarks
related talks
28mUpgrading Rails: The Non-Technical Parts
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
29mUpgrading Rails at Scale
39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0
32mZero downtime Rails upgrades
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
36mRuby & Rails Versioning at Scale
33mUpgrading a big application to Rails 5