standalone image on docker hub
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Looks like the images published on docker hub under iworkflowio/iwf-server-lite and iworkflowio/iwf-server are "all-in-one" images, which are 500MB+, but looking at `docker-compose/docker-compose.yml`, it pulls in temporal separately, so there's no use of such a large image. Might be better to publish a standalone "just iwf server" image.
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 with docker-compose/docker-compose.yml and compare the services it pulls with the contents of the published iworkflowio/iwf-server-lite and iworkflowio/iwf-server images. Then locate the existing image build and publication configuration. Done means a standalone iWF server image is published on Docker Hub without bundling Temporal and remains usable with the compose setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100