Why should I care about RVM's Gemset feature when I use Bundler?
Posted
by
t6d
on Stack Overflow
See other posts from Stack Overflow
or by t6d
Published on 2011-01-14T08:26:43Z
Indexed on
2011/01/14
8:53 UTC
Read the original article
Hit count: 259
I just don't get it. I thought, Bundler was developed to resolve version conflicts between gems. So that I just have to require "bundler/setup"
and everything is fine, knowing that Bundler will load the correct versions of all my gems and their dependencies. Now, RVM is great for managing multiple Rubies, I know, but why should I care about the Gemset feature? Do I miss something here? Can it make my development even easier? Maybe, some of you can give me some hints on the perfect RVM + Bundler workflow for both, development and production.
I also don't know when RVM starts switching to another Ruby. I know that I can have an .rvmrc
file in my project, but do I have to cd
to this directory so that the switch happens?
Furthermore, I usually use Passenger for development since, thanks to the Passenger.prefpane
, integration in Mac OS is great. Can I still do that with RVM or is there a better way to do it? Does Passenger recognize .rvmrc
files and switch to the correct Gemset?
© Stack Overflow or respective owner