chruby
chruby copied to clipboard
Wishlist: integrate with outside Ruby installations like Chef-DK
"Embedded" Ruby environments like Vagrant and the Chef Development Kit have their own ideas for where things are supposed to be placed. Chef-DK in particular has its own preferred settings for PATH
, GEM_ROOT
, GEM_HOME
, and GEM_PATH
that at present don't play well with chruby's method of managing these variables.
Right now I work around this by creating some monster Bash aliases, chefdk
and unchefdk
, that switch between Chef-DK's and chruby's way of doing things. But it would be nice to be able to do it all through chruby (e.g. chruby chefdk
).
We could potentially add a separate file that appends Chef's Ruby to $RUBIES
. I'm not sure how we could handle custom GEM_ROOT
, GEM_HOME
without fundamentally breaking chruby. Also, why do you need to use chruby with Chef's embedded ruby?
Because, for whatever reason, the makers of the vagrant-berkshelf gem insist they won't support its use outside of the Chef Development Kit. But I do not want to be tied to one version of Ruby (the MRI 2.1.4 interpreter that ships with Chef DK).