4 ms·
Not required if you use bundler. But after you are done with the project, there is no easy way to delete the gems that the project uses all at once.
by SingAlong 13y ago
Not required if you use bundler.
But after you are done with the project, there is no easy way to delete the gems that the project uses all at once.
- regularfry 13y agoIt's not required if you use bundler, but I'd argue it's still a good idea. If you can avoid a runtime dependency on bundler, you probably should. > But after you are done with the project, there is no easy way to delete the gems that the project uses all at once. This is part of why I wrote gemenv (https://github.com/regularfry/gemenv.git https://github.com/regularfry/gemenv.git). It gives you a $GEM_HOME in the project directory, in the style of virtualenv.
- crymer11 13y agoIf you bundle install with the `--path` flag (which you should), you can specify the location the gems will be installed (typically something like `--path vendor`) which gives you the ability to easily remove the gems the project uses all at once. Coupled with `bundle package` which stores all the .gem files in vendor/cache, you can ensure that your application always has its gem dependencies available. Here's a great article with more information about all the above: http://ryan.mcgeary.org/2011/02/09/vendor-everything-still-applies/ http://ryan.mcgeary.org/2011/02/09/vendor-everything-still-a...