You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GHPAGES-DOCKER needs to be updated - ruby gem #142
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)
...
@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.
Activity
danielridgebot commentedon Aug 19, 2024
[-]GHPAGES-DOCKER needs to be updated[/-][+]GHPAGES-DOCKER needs to be updated - ruby gem[/+]roslynwythe commentedon 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 commentedon 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
mainbecause I'm guessing the code doesn't pin specific versions of ruby packages, causing ruby complains aboutrubygems-updaterequiringruby >= 3.0.0, which it doesn't have.So I only built the updated PR branch.
Then went into the image to check the gem versions
So that looks good.
fyliu commentedon 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:testingimage to the public and ask people to test that before merging? The website repo docker-compose file points tohackforlaops/ghpages:latest.fyliu commentedon 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...
roslynwythe commentedon Aug 26, 2024
ExperimentsInHonesty commentedon Oct 7, 2024
added it to my website team agenda hackforla/website#2607 (comment)