swagger-api / swagger-api/swagger-ui
Publish to non dockerhub repository
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Using dockerhub images is a problem for a lot of places, due to the very harsh rate limiting they impose. This forces us to mirror the swagger-ui image into our private ECR in order to utilize it for builds.
It would make everyone's lives easier if the swagger-ui docker image was published to a non dockerhub container registry. Alternatives include:
- Google artifact registry
- Github container registry
- Quay.io
Contributor guide
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 reviewing the existing Docker image publishing workflow and the registry options listed in the issue: Google Artifact Registry, GitHub Container Registry, and Quay.io. The work is done when the swagger-ui image is published to a non-DockerHub registry and the resulting image can be used for builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100