librespeed / librespeed/speedtest-go
Docker hub image publishing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 875
- Forks
- 183
- PR merge metrics
- No merged PRs in 30d
Description
Description
Automatically publishing images, ideally using the same librespeed/speedtest-go naming allows an easy 'straight from the source' install. Some CI, like GH actions makes this pretty easy. Especially when you're already maintaining a Dockerfile.
Why it should be implemented
I believe, https://hub.docker.com/r/mickkael/librespeed-go is the closest to an "official" image being published?
It's a bit of a mess of people building their own speedtest-go/librespeed-go images.
And the mickkael/librespeed-go one seems out of date, rocking v1.1.3, so I assume it is being pushed manually from a dev machine.
For reference a modern multi-arch GH action might look something like this. https://github.com/thomseddon/traefik-forward-auth/pull/275
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing Dockerfile and GitHub Actions configuration. Determine how images should be built and published under the librespeed/speedtest-go name, including the requested multi-architecture behavior; done means the workflow publishes current images reliably to Docker Hub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100