Run playground in container
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
as title
Describe the feature you'd like:
run tidb playground in one container
Why the featue is needed:
Many individual developers cannot afford the high price of the TiDB-cluster, but they may want to use related tools from the TiDB community.
For example, the TiDB dashboard / one-click Grafana monitor etc.
Consider that tiup already provides "tiup --tag xxx playground" to ensure that data is not lost.
Perhaps we could go a step further and provide docker images to help individual developers replace their mysql with tidb playground ?
By the way I think we can think of TiDB-playground as a lighter version of TiDB-cluster, e.g. the relationship between K3s and K8s
Describe alternatives you've considered:
I found this repo, which may help a little
Teachability, Documentation, Adoption, Migration Strategy:
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 tiup --tag xxx playground flow and the referenced yeya24/tidb-playground repository. Define the container scope, including whether TiDB Dashboard, Grafana monitoring, and persistent data are required. Done should mean the playground can be started in a container with the agreed tools and data-retention behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100