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

Update Dockerfile (and Ruby version) #1874

Closed
wants to merge 3 commits into from

Conversation

gnclmorais
Copy link
Contributor

@biggianteye pointed out to us that our Docker instructions were no longer up to date, running into a few issues while trying to set the website up using them. This commit updates the Ruby version slightly so that we can use another Docker image as a base. Fixes #1869

@gnclmorais
Copy link
Contributor Author

Since we’re at it… @matyikriszta, what do you think of our GitHub Actions using the Dockerfile to setup everything and run the tests, kind of like this example? This way, we “fill two needs with one deed”: we continuously test our Docker setup and make sure our tests run.

@biggianteye pointed out to us that our Docker instructions were
no longer up to date, running into a few issues while trying to
set the website up using them. This commit updates the Ruby version
slightly so that we can use another Docker image as a base.

Fixes codebar#1869
I’ve found this message to be useless while tests are running, it
clutters the terminal.
These two messages would appear on some tests, on the console. With
this commit those messages are still caught but don’t show up on the
console anymore (in the middle of RSpec’s dots).

The messages were:
- You have to provide an email address. Usage: rake member:delete'[email@address.com]'
- Checking for expected text of nil is confusing and/or pointless since it will always
  match. Please specify a string or regexp instead.

Technically, the second one is not a message we display on the code,
but rather an RSpec warning telling us one of our variables was nil.
Adding content to the constructor was the solution.
@matyikriszta
Copy link
Contributor

@gnclmorais I merged in #1877, the priority was to get deployment working again. Could you rebase this PR on master and incorporate those changes?

@gnclmorais
Copy link
Contributor Author

#1882 already deal with this, so I’m closing the PR.

@gnclmorais gnclmorais closed this Jul 30, 2023
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.

Fresh project setup fails because of out of support base operating system
2 participants