Kay, rbenv problem we can't seem to figure out.
rbenv version acknowledges that we're using 2.4.1
But bundle install --deployment --without development test says we're using 2.3.3
Which is just super frustrating.
We've modified bashrc and we're kinda at a loss now tbh
@spiderrobotpig *sigh* sorry wish I could help, I haven't used rbenv in a while, shifted to chruby 2 yrs ago, forgot everything.
@Rtzq0 It's just seriously being a pain haha
@spiderrobotpig erm so I'm not a ruby person. 'which' just says executable is going to be executed for the executable name if you don't specify an absolute path. how about 'which bundle' ?
@Rtzq0 /usr/local/bin/bundle
@spiderrobotpig Okay so my guess is that you have a 'system' bundle gem (that goes with your system ruby). can you gem install bundler and then run which bundle again?
@Rtzq0 /home/spiderrobotpig/.rbenv/shims/bundle
now it's this which seems better?
@spiderrobotpig HAHA so basically (apparently, I was hoping) rbenv works the same way as python's virtualenv which is that if you don't have a gem installed for your 'current running' ruby it falls through to the 'system' version (whatever is installed globally).
@Rtzq0 It's weird though because we tried running it after we did the reinstall and it still didn't work?
But we restarted terminal too so maybe that helped
@Rtzq0 Holy crap that worked
@spiderrobotpig 1/2 catastrophic failures to chooch remediated today. Now off to the noodle house.
@spiderrobotpig what do you get, out of curiosity, when you type 'which ruby' ?