ClickHouse / ClickHouse/clickhouse-fiddle
Fiddle roadmap 2026
- Dominant language
- Go
- Stars
- 74
- Forks
- 12
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 16
Description
- [ ] Deployment through GitHub actions
- [ ] Monitoring for instance unavailability
- [ ] Add `users.xml` and `config.xml` tabs to override any setting
- [ ] More tests (at least check the Docker image builds) on the PR stage
- [ ] Migrate from DynamoDB to ClickHouse Cloud
- [ ] Monitoring: use Prometheus scraper to send the metrics over to ClickHouse using remote-write
- [ ] Migrate to Kubernetes
- [ ] Cache Docker images in S3
- [ ] Being able to chose builds from PRs directly: https://github.com/ClickHouse/clickhouse-fiddle/issues/52
- [ ] Public API: https://github.com/ClickHouse/clickhouse-fiddle/issues/72
Contributor guide
No contributing guide indexed for this repository
Research direction
This issue is a broad roadmap rather than a single contribution. Start by reading the linked issues about choosing builds from PRs (#52) and the public API (#72), then separate the checklist into independently scoped tasks. Done cannot be determined for the roadmap as a whole because it has no single acceptance criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, docker, github-actions, go, kubernetes, prometheus
- Domain
- api, ci-cd, cloud, databases, devops, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100