matomo-org / matomo-org/docker
Push Docker images into the GitHub Container Registry
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1k
- Forks
- 384
- PR merge metrics
- No merged PRs in 30d
Description
I saw that this repository is configured to run GitHub Actions to build Docker images.
But for the moment it only tests if the Docker image build successfully, but they are not pushed anywhere.
It could be nice to be able to test Docker images before they are released into the official Docker images in the Docker Hub.
I suggest that we push those Docker images into the [GitHub Container Registry](https://docs.github.com/en/free-pro-team@latest/packages/getting-started-with-github-container-registry/about-github-container-registry) or in the Docker Hub in a custom organization.
I can help you to set up that if you want.
@J0WI it seems that you are in charge of the Docker images part. What do you think about that?
This could help for #221.
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 reading the existing GitHub Actions workflow that builds the Docker images and inspect how image names and release timing are defined. Confirm the registry authentication and publishing requirements for GitHub Container Registry. Done means test-built images are available in the selected registry without replacing the official Docker Hub release flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100