Publish container image to quay.io/azavea account
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In order to save users the step of having to build the image locally.
Not pressing, as build times aren't long, but a nice to have at some point.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the repository's Docker image definition and any existing build or release workflow, then determine how an image can be published to the quay.io/azavea account; done means users can pull the published image instead of building it locally.
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