-
-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi ruby devcontainer setup #2568
Conversation
b51ff06
to
78907d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is an interesting idea. Can you also describe the process you use to switch between Rubies with this setup? I think it's probably worth documented in CONTRIBUTING.md
?
b9ed90e
to
5a818c5
Compare
@st0012 I updated the CONTRIBUTING file - would you mind checking out this branch and seeing if you can get up and running with the devcontainer? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't use vscode but totally okay with merging in a better tooling experience.
I'll also try to see if I can use these without vscode.
5a818c5
to
371a5c1
Compare
I struggled a lot when switching between rubies to test things out / fix specs etc. so I ended up with a devcontainer setup that allows me to easily switch to a specific ruby version in VS Code.
I figured I could share this here because it may turn out to be useful for others.
The reason why this is based on devcontainers is simple - we support too many rubies that have conflicting dependencies. I could not use rvm or any other Ruby version manager to easily switch between super old crubies or jruby.
Furthermore, I think we could have a nice setup with relay running as a docker service which can really help with figuring things out with envelopes etc.
#skip-changelog