MapColonies / MapColonies/microcOSM
Determine the containers' readiness
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Each container's readiness should be determined when it depends on other components in the stack.
At the moment we use bash sleep in a crude way.
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
The issue names no files or tests. Start by locating the container definitions and startup commands, then trace dependencies between services and the existing bash sleep. Done means dependent containers wait on readiness conditions rather than a fixed delay, with the relevant startup checks exercised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100