Readme says Ruby 2.1.8 or newer, but actually need exactly 2.1.8

Because the gitlab subdirectory has a .ruby-version saying 2.1.8, if you're using rbenv, and possibly rvm, you have to have exactly Ruby 2.1.8, but the readme says:

Ruby 2.1.8 or newer installed with a Ruby version manager (RVM, rbenv, chruby, etc.), DO NOT use the system Ruby

I'm not sure if rvm and chruby aren't as strict, but if they are, then perhaps the readme should remove "or newer"?

@markpundsack when using the GDK's ./run command, it doesn't seem to care about .ruby-version. Not sure if that's an RVM thing, though.

Interesting. I wonder if I saw that only when I manually did bundle exec rake dev:setup and not when doing .run.

@connorshea I am sorry to hear .ruby-version is not working; I am not sure what else we can do to fix it. (BTW not working with which Ruby switcher?)

We currently have a .ruby-version in the GDK root which is just a symlink to gitlab/.ruby-version.

I have pushed cdf2e846 to say we want Ruby 2.1.

FWIW it is not run's job to care about .ruby-version, I think, but rather the job of whatever Ruby version manager you are using. run and Foreman (the Procfile) do not / should not change the PATH in a way that changes how ruby is found.

@jacobvosmaer I consider it a feature more than a bug :P Good for testing 2.3.0 compatibility.

Status changed to closed

@connorshea OK!

Closing because the README specifies Ruby 2.1 now.