From FTP to Kamal: 20 Years of Deploying Rails
summary
Traces 20 years of Rails deployment from FTP and CGI to Mongrel’s C HTTP parser, FastCGI fragility, Passenger isolating apps inside nginx, Capistrano automating SSH-based releases, Heroku turning ops into a one-liner and Puma/Unicorn changing concurrency models. Claims Docker finally solves Ruby-version drift and Kamal replaces Capistrano with containerized releases. Notes surprising reliability improvements and persistent pain points: process crashes, memory leaks, and the moment most remember as git push heroku alongside Capistrano and Docker and Kamal.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:34Web dawn and early deployments
- 7:25PHP and shared hosting
- 11:13Rails debut and challenges
- 15:05Mongrel and HTTP servers
- 18:15Capistrano and automation
- 20:41Unicorn, Puma, and servers
- 22:24Heroku and cloud era
- 23:31Docker and containers
- 25:58Summary and call to action
related talks
35mTen Years of Rails Deployment
35mMy Rails App is Old Enough to Drink: Over Two...
07mLightning Talk: How Docker Can Change Rails Deployments
36mContinuous Deployment with Rails
34mGuide to Continuous Deployment with Rails
43mServer Infrastructure for Rails in 2016
49mRuby Software Continuously Delivered and Exhaustively Explained
31mTen Years of Rails Tutorials
