March 6, 2006
Capistrano released
Jamis Buck released Capistrano 1.1 on March 6, 2006 — a RubyA dynamic language emphasizing developer happiness — Rails made it the default for web startups in the 2000s. DSL for automating multi-server application deploys over SSHSecure Shell — encrypted remote login, command execution, and file transfer over networks..
What it was for
Capistrano (renamed from SwitchTower) codified `cap deploy`: git pull, bundle install, migrate database, restart Unicorn — across a fleet of servers with roles and stages. It taught a generation of Rails teams that deployment should be scripted, repeatable, and boring. Chef, Ansible, and later containerAn isolated runtime environment packaging an app and its dependencies — lighter than full virtual machines. rollouts extended the same idea at larger scale.
Why it's here
Capistrano made scripted multi-server deploys mainstream in the RubyA dynamic language emphasizing developer happiness — Rails made it the default for web startups in the 2000s. web ecosystem.
Why it mattered
It shifted deploys from manual SSHSecure Shell — encrypted remote login, command execution, and file transfer over networks. sessions to version-controlled automationUsing machines or software to perform tasks with minimal human intervention. recipes.
What it solved
TeamsMicrosoft Teams — chat, video calls, and Office integration for workplace collaboration. running Rails on several boxes needed consistent, auditable release steps without hand-typing commands on each host.
Media
- ImageCapistrano (software)
Tom Clements, Lee Hambley, MIT, via Wikimedia Commons
Related
- Ruby 0.95 publicly releasedDecember 21, 1995
- Ruby on Rails open sourcedJuly 24, 2004
- Chef first releasedJanuary 15, 2009
- CircleCI foundedSeptember 1, 2011
- RubyGems releasedMarch 14, 2004
- Phusion Passenger releasedApril 11, 2008