Skip to content
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

Amend ruby version in docker image and documentation #750

Merged
merged 1 commit into from
May 9, 2024

Conversation

haydenrou
Copy link
Collaborator

No description provided.

@haydenrou haydenrou self-assigned this Apr 18, 2024
@@ -1,6 +1,6 @@
source "https://rubygems.org"

ruby file: ".ruby-version"
ruby "3.2.3"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@compwron I note this change was made specifically here: ae10663 - do you see any harm in changing it to be a hard-coded version?

The reason I did this was that I was getting the following error in docker and this was the easiest fix to unblock me
Screenshot 2024-04-18 at 11 41 19

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to add the .ruby-version file to the Dockerfile context?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so. And personally i like hardcoding it too -- .ruby-version is really for your editor and maybe its better to globally git ignore your preferred toolset (I like asdf for example, so i get .tool-versions)

Gemfile will stop and give the right error message if your Ruby is wrong version and changing ruby to ME is something you just do

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes - I believe you're right in terms of fixing the error screenshot I posted.
Saying that, I don't feel strongly either way whether this should be hard-coded or linked to the .ruby-version file. I do agree however that it can get confusing having multiple files determining versions.
I personally use .tool-versions, but I think the dockerisation can be agnostic of this.

@haydenrou haydenrou requested a review from compwron April 18, 2024 15:46
Copy link
Collaborator

@johnpaulashenfelter johnpaulashenfelter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm in favor of this 👍

@@ -1,6 +1,6 @@
source "https://rubygems.org"

ruby file: ".ruby-version"
ruby "3.2.3"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so. And personally i like hardcoding it too -- .ruby-version is really for your editor and maybe its better to globally git ignore your preferred toolset (I like asdf for example, so i get .tool-versions)

Gemfile will stop and give the right error message if your Ruby is wrong version and changing ruby to ME is something you just do

@compwron compwron merged commit 70e58e7 into master May 9, 2024
12 checks passed
@compwron compwron deleted the quickfix/ruby-version branch May 9, 2024 18:06
@compwron
Copy link
Collaborator

compwron commented May 9, 2024

Seems fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants