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@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 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 it's computer science! the mysticism of unraveling mystery