Ensure site works under Ruby 3.4.3

[pieterdd]

I had trouble getting the site up and running locally. It seems the issues were related to dated dependencies.

[hellcp]

@tacerus we are still running under ruby 3.1 on the server side like in the Ci, right?

[pieterdd]

Are you building the site again on a server? I see that you've already got a GitHub Actions generating the static assets. If that's easier on server end, I could ensure the static assets are exposed as artifacts in the GitHub workflow so they can be downloaded and deployed as-is on any Apache. Then you don't need to couple the build process to a specific Ruby version that runs on the server.

Unrelated note: it looks like Rubygem's mirrors are currently unstable. I got SocketError: Failed to open TCP connection to mirror.rackspace.com:443 (getaddrinfo: Try again) in the build, so I'm trying to work around that.

[tacerus]

@hellcp Yup: https://github.com/openSUSE/heroes-salt/blob/9e0d9880ac271f606d81f1917d288d3a5718e715/salt/profile/jekyll/files/git_pull_and_update.sh.jinja#L32.

[hellcp]

Will be necessary to make it work with both versions then if you want to update the dependencies

[pieterdd]

I've integrated the generation of the website assets into a GitHub action and made sure it uses a recent Ruby version. There are two ways to get the generated assets:

• Open the 'Generate website' status check, expand 'Save artifacts', click the link
• Run curl https://api.github.com/repos/opensuse/get-o-o/actions/artifacts?name=website | jq -r '.artifacts | map(select(.workflow_run.head_branch == "main"))[0].archive_download_url' on your server to get the URL of the ZIP file containing the assets. Note that this won't work yet because there's no build on main yet. Replace main with update-dependencies if you want to see it in action. This command requires jq, a JSON parser.

Would this work for you?

[hellcp]

Updated the main branch with support for both ruby 3.1 and 3.4 (tested both locally) 285346c