To prevent bin/setup from failing because the user is using the incorrect Ruby version, we can let rvm choose what ruby to use.
I didn't think this was necessary since the Docker image alreadysources rvm. You can even arrow up in a new Gitpod workspace and see the source command in the Bash history... Regardless, now when the project is initialized, we source the rvm and then exit and re-enter the project folder so the correct Ruby version is selected. Finally bin/setup will run.
To prevent
bin/setup
from failing because the user is using the incorrect Ruby version, we can letrvm
choose what ruby to use.I didn't think this was necessary since the Docker image already
source
srvm
. You can even arrow up in a new Gitpod workspace and see thesource
command in the Bash history... Regardless, now when the project is initialized, we source thervm
and then exit and re-enter the project folder so the correct Ruby version is selected. Finallybin/setup
will run.