When Bundler Insists On Putting Gems into vendor/cache
source link: https://fuzzyblog.io/blog/rails/2016/11/06/when-bundler-insists-on-putting-gems-into-vendor-cache.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
When Bundler Insists On Putting Gems into vendor/cache
Nov 6, 2016
If you've ever find that Bundler insists on putting gems in vendor/cache and you can't make it stop, check the .bundle/config file and you will find a directive that was written there as a result of a bundle install –path vendor/bundle command you did previously. Once you execute this command, bundler will write gems to this directory forever more unless you delete the directive. This can be maddening as .bundle/config isn't a file that many of us look at.
Notes:
- Bundler Reference
- Thanks to Dv who pitched in on this on a busy Sunday morning
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK