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
@Rtzq0 It's just seriously being a pain haha
@spiderrobotpig what do you get, out of curiosity, when you type 'which ruby' ?
@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@spiderrobotpig-Aspire-F5-573G:~$ ruby -v
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
Seriously what kind of sorcery is this?
@spiderrobotpig it's computer science! the mysticism of unraveling mystery
@spiderrobotpig after you modify the bashrc, you need to log out and log in for the change to take effect.
@asonix ....goddamnit.
WHY ARE WE SUCH NOOB
@spiderrobotpig its okay! These are things I've picked up after years of linuxing and developing
@asonix Totally didn't work though.
Still giving the error >.>
@asonix It's working now for some reason
@spiderrobotpig check the path for bundler. Check the top line of the file. Or just gem install it again just in case.
@halkeye Did a gem install again after a reboot and it didn't do anything
@halkeye IT IS ALIIIIIIIIIIIIIIIIIIVE
@spiderrobotpig :heart_eyes: :heart_eyes: :heart_eyes: :heart_eyes:
@spiderrobotpig I think you need to `rbenv system 2.4.1` to update all the links... (might be global instead of system; I don't remember at the moment, since I've been focused on instances with Nanobox instead, and that bypasses the entire rbenv circus.)
@spiderrobotpig I don't actually know if that'll give you the answer but it looks promising.
@spiderrobotpig try running "gem install bundle" if you used "gem install bundler" already then try running the bundle install
@geektox Yeah, that was suggested, and we also did a restart in case that was goofinf it.
Wish us lucj we guess haha
@geektox Nope, still giving me the error
@spiderrobotpig That's frustrating... I had the same problem when I was updating earlier and gem install bundle fixed it :< I'm no sysadmin so I don't think I can help more, sorry!
@geektox Yeah, it actually decided to run right after we messaged you haha
it's working now
@spiderrobotpig Hurray! Computers!
@spiderrobotpig *sigh* sorry wish I could help, I haven't used rbenv in a while, shifted to chruby 2 yrs ago, forgot everything.