temporalio / temporalio/temporal
Docker: Docker image with schema loaded
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
The initial execution of the docker-compose up takes a long time. Mostly because it has to create the DB schema. Consider shipping a docker container with a schema already populated to speed up the startup.
Any other ideas on how to speed up docker-compose up are welcome.
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 tracing the docker-compose up path and identifying where the database schema is created during initial startup. Compare the available container and schema-loading steps, then define a faster startup path that preserves a usable populated schema. Done means a fresh docker-compose up completes faster with the expected database schema available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100