11 engineers on Hacker News describe using Capistrano first-hand: 3 endorse it, 1 regret it, 3 are mixed.
“Longtime Capistrano user, loves Docker for reproducible environments”
endorse · production · sickcodebruh · 2023-04-29 · source ↗ · wrong label?“Capistrano really has saved us multiple times, sad that a vocal part of the community tends to exhibit such behavior.”
endorse · production · joaomsa · 2013-10-07 · source ↗ · wrong label?“as Capistrano sits on the boundary of where these problems come to light, it seems to fall to us to deal with it”
mixed · production · codebeaker · 2013-10-06 · source ↗ · wrong label?“company where I work we use it for deploying java, php, ruby and all sort of stuff... various releases of v2 were buggy.”
mixed · production · gnufied · 2013-10-06 · source ↗ · wrong label?“Capistrano is better for the simple stuff, but once we started doing more we moved to phing.”
mixed · production · atstsolutions · 2010-10-14 · source ↗ · wrong label?“+1 for Capistrano, we use it to deploy Rails, Sinatra, and PHP apps.”
endorse · production · zackham · 2010-10-14 · source ↗ · wrong label?“couldn't get my co-workers up-and-running with it so we switched to using Phing”
regret · production · grumpycanuck · 2010-10-14 · source ↗ · wrong label?“I used to deploy with capistrano, then we moved to deploy it from a single rpm file”
neutral · production · pelasaco · 2023-01-26 · source ↗ · wrong label?“use Capistrano to deploy”
neutral · production · TheRealDunkirk · 2021-12-16 · source ↗ · wrong label?“Then, we send out `master` via `cap staging deploy` and `cap production deploy`.”
neutral · production · ericclemmons · 2013-10-11 · source ↗ · wrong label?“run migrations on production prior to Capistrano deploys, etc.”
neutral · production · devmonk · 2010-11-15 · source ↗ · wrong label?