In a rails Gemfile, does gem 'capistrano'
need to be inside the :development
group or this there any advantage in putting it inside an arbitrary group like :tools
?
相关问题
- Question marks after images and js/css files in ra
- Using :remote => true with hover event
- Eager-loading association count with Arel (Rails 3
- Is there a way to remove IDV Tags from an AIFF fil
- gem cleanup shows error: Unable to uninstall bundl
相关文章
- Right way to deploy Rails + Puma + Postgres app to
- AWS S3 in rails - how to set the s3_signature_vers
- how to call a active record named scope with a str
- How to add a JSON column in MySQL with Rails 5 Mig
- “No explicit conversion of Symbol into String” for
- form_for wrong number of arguments in rails 4
- Rspec controller error expecting <“index”> but
- Factory_girl has_one relation with validates_prese
Simply put, no, it doesn't need to be, but it's good for the sake of best practices and keeping your gemsets uncluttered. The best way to do that is open for debate, but basically as long as Capistrano is available to you in the environment you're working in, it doesn't matter what groups it is or isn't associated with, though I can see little to no advantage of using an arbitrary
:tools
group since:development
will exclude it in production cleanly and "auto-magically" in the first place.