Repository navigation
feat(channels): add the YunoHost app catalog - #1034
Merged
Merged
Conversation
YunoHost/apps#3618 merged this morning, so libredb_studio is in that catalog and the inventory should say so. The entry is tier 3, category paas-catalogs, and the one thing that sets it apart from the other self-hosting catalogs here is that it installs no container: the package unpacks the standalone Linux tarball under systemd and pulls its own Node 24 through YunoHost's n. That is why platforms is linux rather than container, and why runtime is channel_supplied. The package repository lives in the YunoHost-Apps organization, so a bump is a pull request there rather than here, and their autoupdate cron opens one when a matching release asset appears. The pin reads the application version past the ~ynh packaging suffix, so a packaging-only revision does not read as drift. docs/CHANNELS.md and src/lib/distribution/channels.generated.ts are regenerated. docs/BRAND_MESSAGING.md carries the channel count by hand and cites CHANNELS.md as its source, so both of its lines move with it; #1009 had to clean that up separately after the Civo merge.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
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.
YunoHost/apps#3618merged this morning, solibredb_studiois in that catalog and the inventory should say so. This adds the channel and regenerates what derives from it.The entry
Tier 3,
paas-catalogs,one-click-template,status: live.One field is not what the neighbouring entries use, and it is the interesting part. Umbrel, CasaOS and Portainer are all
platforms: [container]because they install a Docker container. YunoHost does not: the package unpacks the standalone Linux tarball, runs it under systemd, and pulls its own Node 24 through YunoHost'sn. Soplatformsis[linux], andruntimeischannel_suppliedbecause the channel is what provides the Node.The package repository is
YunoHost-Apps/libredb_studio_ynh. It was written for this release, opened underlibredb, and transferred on the maintainer's invitation, which is how that catalog prefers it and is what brings their CI and their packagers. A bump is therefore a pull request against that repository rather than this one, and their autoupdate cron opens one when a release asset matching the manifest pattern appears.What I verified
state = "working"and the url in the liveapps.toml. The pin's regex run by hand against the livemanifest.toml: one match,0.16.1, equal topackage.json. It reads past the~ynhsuffix deliberately, so a packaging-only revision does not surface as drift.distribution-check.mjsreportsOK | yunohost | 3 | 0.16.1 | 0.16.1, and no other channel's row moved.format,lint,typecheckandtest:unitall pass, as dodistribution:matrix --checkandchannels:showcase:check.One thing to know
https://apps.yunohost.org/app/libredb_studiois a 404 for a few more hours. Their catalog is rebuilt on a cron and the merge was 23 minutes before I wrote this, so the page has not been generated yet. The entry sayslivebecauseapps.tomllists it, which is the catalog's own source of truth, and the note records the build lag the way theunraid-caentry records the Community Applications one.Why BRAND_MESSAGING.md is in here
It carries the channel count by hand and names
docs/CHANNELS.mdas its source, so this change makes both of its lines disagree with that source. #1009 had to clean exactly this up after the Civo merge; no CI gate reads that file.