My Rails App is Old Enough to Drink: Over Two...
summary
An app runs the same codebase for 24 years and still serves a weekly newspaper feature, originally sending TIFFs on CDs. It starts in ColdFusion and migrates from ColdFusion to Rails around 2005, adopts Selenium tests, Capistrano deploys and Heroku-era conventions, and keeps MySQL still in production despite UTF-8/emoji pain. Today it runs Ruby 3.2 and Rails 7.1 on an Ubuntu AMI with Nginx + Passenger, maintained by one developer and still working.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:26Rails app in 2000
- 4:38Rails revolution 2005
- 9:12Early Rails features
- 16:16Rails ecosystem changes
- 22:16Ruby and Rails community
- 25:26Evolution of the Rails app over two decades
- 27:15Lessons from 24 years
- 32:34Renaissance developer
- 33:57Solving problems with Rails
related talks
35mTen Years of Rails Deployment
46mAncient Rails
20mSafely Decomposing a Highly Available Rails App
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
09mMicrotalk:A House of Cards - The Perils of Maintaining a 7-Year-Old Codebase
26mFrom FTP to Kamal: 20 Years of Deploying Rails
36mWorking Compassionately with Legacy Code
26mKeeping the Rails Magic Alive After 18 Years