4 ms·
As I said elsethread, I haven't yet considered production, but I just switched to chruby for my development environment rather than rbenv. I still use ruby-buil
by halostatue 13y ago
As I said elsethread, I haven't yet considered production, but I just switched to chruby for my development environment rather than rbenv. I still use ruby-build when I need (I just needed a version not supported by ruby-install), but I have switched wholesale to chruby, and having found chgems in researching a different answer, I may look at using that as well.
chruby really is the simplest possible thing you can do to solve this problem, and in combinations with chgems, it solves isolation better than RVM does without the brittleness of the shims that rbenv has (ultimately why I moved away from rbenv). Installs are substantially easier with ruby-install and/or ruby-build, although RVM is probably better at this part in general. Extract that out from RVM and I'd consider using it.
- regularfry 13y agoI'd argue that you don't need any of rvm/rbenv/chruby in production.
- halostatue 13y agoI'd agree. Something as simple as chruby makes having multiple interpreter/gemset versions easily usable from something like cron without introducing a lot more overhead, though, or having to remember to put all the variables &c. in place everywhere you need them.