You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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).
The text was updated successfully, but these errors were encountered:
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?
"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
, andGEM_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
andunchefdk
, 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
).The text was updated successfully, but these errors were encountered: