Use github ci to build a container so we can pull it from a registry
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
it would be nice to host the containers prebuilt somewhere. You could use the github ci or travis (as you use it for testing) and deploy the containers to a registry of choice (dockerhub, github registry,...).
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
Inspect the repository's existing container setup and Travis testing configuration first, then compare the proposed GitHub CI and registry options mentioned in the issue. Done means the project containers are built automatically and can be pulled from a chosen registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100