No need to include capistrano gem when using capistrano-rails

[robinroestenburg]

Also see issue: capistrano/capistrano#582

When using capistrano-rails there is no need to include the capistrano gem. The only reason to include it is probably because you want to use a specific version.

[Kriechi]

👍

[kirs]

That's not verbose for me at all.
I'm using capistrano framework to deploy, not capistrano-rails.

With the same logic you should remove gem 'rails' from your Gemfile because some other gems are already dependent on Rails.

[Kriechi]

Mhm, on the same side one could argue that capistrano-rails should already include capistrano-bundler, since Rails3 and 4 use it by default.

@kirs though decision, should capistrano-rails be a one-stop-solution?
or more like a little tool to help build something bigger?

In the current capistrano-* universe I already have to include capistrano-rails, capistrano-bundler and capistrano-rvm gems... And capistrano itself of course.

[kirs]

I agree that it would be nice to add capistrano-bundler as dependency for capistrano-rails, but developers will still have to require it manually in Capfile.

[seenmyfate]

I'm going to close this as this looks to be covered by #22