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.
This was referenced Sep 28, 2026
cevheri
added a commit
to libredb/libredb-studio
that referenced
this pull request
Sep 28, 2026
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.
Author
|
Hi all, any update this PR |
Author
|
this guy is your team ? : libredb/libredb-studio#1183 (comment) |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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