Use Ruby Bundler to build only non-development, non-test gems?
Question
I'm building an Iron.IO Ruby-only application and as part of their new docker workflow, I need to run bundler to build the bundled gems into ./bundle locally. However, it builds all the gems, including the group 'development' and group 'test' gems. It's wasted data so I'd like to be able to do a clean build of only the gems I actually need.
Is there a way to tell bundler to only build the non-dev, non-test gems?
1 answers
solution1
1 ACCPTED 2015-12-07 03:27:34
bundle install --without development test
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Bundler in production not ignoring the development and test gems
Referencing multiple local ruby gems in development using Bundler
Bypassing bundler for auxiliary development gems
How bundler isolates gems in Ruby?
Is there a way to use Bundler for production gems?
bundler, rubygems and dynamic use of gems
requiring non-core ruby gems for apache cgi scripts
Installing Gems on Amazon AWS with Elastic Beanstalk for non Rails ruby script
Non specific MVC framework ruby gems and example code to Rails framework
If Bundler installs gems in a non-standard path, how do I get access to those gems and any bin files they come with?
Related Tags