Best Practices for Vendoring Ruby Gems
Best Practices for Vendoring Ruby Gems
by
·
Join the DZone community and get the full member experience.
Join For FreeKeeping your dependencies with your application can save time and effort when switching between multiple projects, especially amongst a team of developers. Balazs Nagy, a part-time Rails developer, explains how to solve this issue by vendoring his Ruby gems. He demonstrates his best practices for vendoring his gems "with style":
1. We use rvm
2. However, we got rid of it’s bundler helpers
3. We don’t rely on the bundler pool using executables / scripts
4. … but we have a pool, and we don’t have multiple copies the same gems (ssd is still not cheap)
5. Most shortcomings of vendoring gems are hidden
Nagy only found one issue with the guard-bundler, which was fixed with a recent update. The full blog post includes an in-depth walk-through and code examples explaining his gem vendoring method.
Like This Article? Read More From DZone
Published at DZone with permission of Ross Jernigan . See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}