3

When Bundler Insists On Putting Gems into vendor/cache

 3 years ago
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.
neoserver,ios ssh client

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:


Posted In: #rails #ruby #bundler #gem


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK