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

GHPAGES-DOCKER needs to be updated - ruby gem #142

Closed
danielridgebot opened this issue Aug 15, 2024 · 7 comments · Fixed by hackforla/ghpages-docker#3
Closed

GHPAGES-DOCKER needs to be updated - ruby gem #142

danielridgebot opened this issue Aug 15, 2024 · 7 comments · Fixed by hackforla/ghpages-docker#3

Comments

@danielridgebot
Copy link

GitHub Pages is now using v3.3.4 of Ruby. You are using v2.7. Please refer to the ghpages-docker Wiki for instructions on how to update.

@danielridgebot
Copy link
Author

@danielridgebot danielridgebot changed the title GHPAGES-DOCKER needs to be updated GHPAGES-DOCKER needs to be updated - ruby gem Aug 19, 2024
@roslynwythe roslynwythe self-assigned this Aug 19, 2024
@roslynwythe
Copy link
Member

roslynwythe commented Aug 19, 2024

@fyliu I updated the Dockerfile in my fork and created a PR hackforla/ghpages-docker#3 but please advise how/when will we test?

@fyliu
Copy link
Member

fyliu commented Aug 19, 2024

@roslynwythe

I was going to run the website code with the old and then the new image to see that they both work. Are there specific things that's good to check on?

It turns out I can't build the old image from main because I'm guessing the code doesn't pin specific versions of ruby packages, causing ruby complains about rubygems-update requiring ruby >= 3.0.0, which it doesn't have.

So I only built the updated PR branch.

# build the image with the existing <repo>/<name> but with a testing tag
docker build -t hackforlaops/ghpages:testing .

Then went into the image to check the gem versions

docker run -it hackforlaops/ghpages:testing sh

# inside the container
# check ruby version
ruby --version

# output
ruby 3.3.4 ...

# check gem version
gem list | grep github-pages

# output
github-pages (232)
...

So that looks good.

@fyliu
Copy link
Member

fyliu commented Aug 19, 2024

@roslynwythe
I think I should approve the PR if the website looks okay and you can do further testing and merge it when you feel it's ready.

Maybe find some website team members to try it? Or would it be better to push a hackforlaops/ghpages:testing image to the public and ask people to test that before merging? The website repo docker-compose file points to hackforlaops/ghpages:latest.

@github-project-automation github-project-automation bot moved this to New Issue Review in CoP: DevOps: Project Board Aug 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Review to In progress (actively working) in CoP: DevOps: Project Board Aug 20, 2024
@fyliu
Copy link
Member

fyliu commented Aug 21, 2024

@roslynwythe
I think your message disappeared, but it looked right. It's probably its own separate issue though.

Since it's a separate workflow file, it's probably okay to tack on an automation to push a test image when a PR is approved. Something like...

on:
  workflow_dispatch:
  pull_request_review:
    types: [submitted]
jobs:
  build:
    if: github.event.pull_request_review == 'submitted' && github.event.review.state == 'approved'
    runs-on: ubuntu-latest
    steps: ...

@roslynwythe
Copy link
Member

roslynwythe commented Aug 26, 2024

@ExperimentsInHonesty
Copy link
Member

added it to my website team agenda hackforla/website#2607 (comment)

@ExperimentsInHonesty ExperimentsInHonesty added the Status: Updated No blockers and update is ready for review label Oct 7, 2024
@github-project-automation github-project-automation bot moved this from In progress (actively working) to Done in CoP: DevOps: Project Board Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

4 participants