3 ms·
> the GPL is recognised to be a dinosaur that has little bearing in modern software infrastructures If I needed any more reason not to use Capistrano, this is
by nilved 13y ago
> the GPL is recognised to be a dinosaur that has little bearing in modern software infrastructures
If I needed any more reason not to use Capistrano, this is it. But I need to wonder why people still use such outdated and poorly implemented instruments as Capistrano in 2014. I speak for myself only, but we have about 200 websites that use Capistrano at my work, each with its own 50-line Capfile, that is subtly broken depending on which Capistrano version you use. Every 2.x release is broken in a different way such that we have an index of which exact version of Capistrano (down to the patch level) works because the rest don't. 3.x is backwards incompatible and infeasible to upgrade at this scale.
git-based deployment takes five seconds to set up and leverages the existing infrastructure instead of creating a feeble reinvention of the wheel, so maybe we should forget this licensing issue and use other deployment strategies because they're plain better.
- jamesbritt 13y agogit-based deployment takes five seconds to set up and leverages the existing infrastructure instead of creating a feeble reinvention of the wheel Isn't Capistrano basically git-based deployment, wrapped in some DSL-ish commands?
- nilved 13y agoSort of. Capistrano can clone a git repo for your application code, but by git-based deployment I mean via post-receive hooks a la Heroku. For example, a short script that runs `bundle install`, `rake assets:precompile` and restarts your web server. Ultimately, you get a solution like Heroku where you deploy by `git push`ing to the server. Trivial to set up, easier to modify, easier to integrate with your git repository, easier to debug, and isn't _completely broken_. Capistrano compared is all downsides.