Repository navigation
feat(casaos-store): publish our own CasaOS store at /casaos-store - #81
Merged
Merged
Conversation
A user can now add https://libredb.org/casaos-store in CasaOS or ZimaOS under App Store -> Add source and install the current LibreDB Studio from it. Why. The official store carries the app, and a version bump there is a pull request a maintainer merges. Measured on 23 October 2026: our 1.0.0 bump (IceWhaleTech/CasaOS-AppStore#1089) had been open seven days with green checks and nothing asked of us, and that repository merged no pull request at all in the two days before - so the wait is attention, not a defect on our side. The official pull request stays open; both channels land on the same release. This is their own documented third-party path: the official store's README links a third-party store guide and lists third-party stores, and the build here is IceWhaleTech's own `build-appstore-action`, pinned by commit. What is committed. `casaos-store/` is the source we edit. `public/casaos-store/` is the generated output the site serves - committed rather than built at deploy time, so the store answers even if the deploy pipeline changes and so a reviewer reads exactly what is published. `.github/workflows/casaos-store.yml` rebuilds it on a push to the source and on demand, and commits the result only when it changed. Verified locally before this commit, with their tool rather than a reading of their spec: the build produced store.json, index.json carrying 1.0.0, per-architecture compose files, meta.json for eight locales, webp assets and metadata.tar.gz with its sha256; `bun run gate` and `bun run secrets` pass; and `bun run build` serves /casaos-store/index.json from dist. Two small corrections the measurement forced: the action has no `v1` tag (its tags are v1.0.1 to v1.1.3), so it is pinned to v1.1.3's commit like every other action here; and the build writes an image-metadata cache beside its source, which is now ignored rather than committed.
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.
What a user gets
Add
https://libredb.org/casaos-storein CasaOS or ZimaOS under App Store → Add source and install the current LibreDB Studio.Why
The official store carries the app, and a version bump there is a pull request a maintainer merges. Measured on 23 October 2026: our 1.0.0 bump (IceWhaleTech/CasaOS-AppStore#1089) had been open seven days with green checks and nothing asked of us - and that repository merged no pull request at all in the two days before. So the wait is attention, not a defect on our side. The official PR stays open; both channels land on the same release.
This is their own documented third-party path - the official store's README links a third-party store guide and lists third-party stores - and the build is IceWhaleTech's own
build-appstore-action, pinned by commit.What is committed
casaos-store/Apps/LibreDBStudio/)public/casaos-store/.github/workflows/casaos-store.ymlThe output is committed rather than built at deploy time, so the store answers even if the deploy pipeline changes, and a reviewer reads exactly what is published.
Verified locally, with their tool rather than a reading of their spec
store.json,index.jsoncarrying 1.0.0, per-architecture compose files,meta.jsonfor eight locales, webp assets andmetadata.tar.gzwith its sha256;bun run gateandbun run secretspass;bun run buildserves/casaos-store/index.jsonfromdist.Two corrections the measurement forced: the action has no
v1tag (v1.0.1 … v1.1.3), so it is pinned to v1.1.3's commit like every other action here; and the build writes an image-metadata cache beside its source, now ignored rather than committed.