Repository navigation
feat(libredb-studio): add LibreDB Studio application chart - #322
Conversation
LibreDB Studio is an open-source web SQL IDE. The chart runs one pod with its own data in SQLite on a volume, and generates the admin password and JWT secret once, so saved connection passwords stay readable across upgrades and reinstalls.
zopdev/helm-charts#322 lists LibreDB Studio as an application chart on helm.zop.dev and ZopDay. The row stays pending until it merges; the note says what to pin then.
|
Hi all, any update this PR |
|
this guy is your team ? : libredb/libredb-studio#1183 (comment) |
arunesh-j
left a comment
arunesh-j
left a comment
There was a problem hiding this comment.
Thanks for the chart! Three changes inline on values.yaml.
Once these are in, keep the version at 0.0.1 (it isn't released yet) and re-run helm package ./charts/libredb-studio --version v0.0.1 into docs/ and helm repo index . --url https://helm.zop.dev so the tarball and index match.
|
Hi @cevheri, thanks for the chart. I've left a review with three small changes on |
- Replace the image block with a top-level version; the repository is fixed in the template. - Replace persistence with a top-level diskSize; the claim is always created on the default StorageClass. - Default alerts.enabled to false, so an install works without the Prometheus Operator CRDs. Repackage v0.0.1 and regenerate the index.
|
Thanks @arunesh-j, all three are in (d2a9421): a top-level |
Repackage v0.0.1 and regenerate the index.
|
@arunesh-j fixed in 8f85cc0, ready for another look. |
PiyushSingh-ZS
left a comment
PiyushSingh-ZS
left a comment
There was a problem hiding this comment.
README values table: image.pullPolicy, service.type, service.port and ingress.annotations are in values.yaml and the schema but not in the chart README. CONTRIBUTING asks for every overrideable value to be documented there.
Repackage v0.0.1 and regenerate the index.
|
@PiyushSingh-ZS added |
PiyushSingh-ZS
left a comment
PiyushSingh-ZS
left a comment
There was a problem hiding this comment.
Thanks, all values are documented now (pullPolicy went with the image block). LGTM.
|
thanks, I will block libredb organization if not, do you know him? |
|
@cevheri yes she is part of our team |
OK, thanks |
zopdev/helm-charts#322 merged on 6 Oct 2026 and helm.zop.dev serves chart v0.0.1. Flip the channel to live, add the catalog link and a remote_file pin on the upstream Chart.yaml appVersion, and regenerate docs/CHANNELS.md and the login showcase.
3 participants
Adds
charts/libredb-studio, an application chart for LibreDB Studio, an open-source web SQL IDE. Follows up on libredb/libredb-studio#1183, where listing it here was suggested.One pod, no subcharts. Studio keeps its own data (saved connections, queries, history) in SQLite on a PVC, so a first install needs no settings.
A few choices worth a look:
JWT_SECRETare generated once into a Secret and read back withlookup.JWT_SECRETalso seals the saved connection passwords, so the Secret and the PVC both carryhelm.sh/resource-policy: keep.replicas: 1withRecreate, because of SQLite on a ReadWriteOnce volume.auth.insecureCookieis an explicit opt-in, and NOTES warns when the ingress has no TLS.release: prometheusdirectly; the shared label helper would override it.Tested on k3d (Kubernetes 1.35) with kube-prometheus-stack and Helm 3.19:
helm lint --strictclean; default install 1/1 Running, 0 restartsauth.insecureCookie=true