by adom
How the Adom Wiki (wiki.adom.inc) works and how to drive it with the adom-wiki CLI: the two storage layers (git page repo vs package registry), hosting source by pushing files (not a tarball), making packages, cutting per-platform releases, and the three-tier skill layout (user skills ship, dev-skills/ and publish-skills/ stay source-only). adom-wiki is the current tool; adompkg is deprecated.
Download card: pick the file by visitor OS, and offer .deb / .rpm / AppImage on Linux
Request (from John Lauer). Adom Hydrogen is getting a Linux build, shipped from the same page and the same release as the Windows one (adom/hydrogen). A Linux app ships as three packages, not one, so the page's download card needs to know the visitor's OS and offer a choice on Linux.
Today. A release holds several assets, each tagged with --platform any|linux|macos|windows and --arch. 1.0.705 has one asset, Adom.Hydrogen_1.0.705_x64-setup.exe (windows/x64). The download card promotes one file. A Linux release adds three assets that are all linux/x64, and nothing tells them apart:
adom-hydrogen_1.0.710_amd64.deb(Ubuntu, Debian, Mint, Pop!_OS)adom-hydrogen-1.0.710.x86_64.rpm(Fedora, RHEL, openSUSE)Adom_Hydrogen-1.0.710-x86_64.AppImage(any other Linux)
What we need.
- The card picks by visitor OS. Windows visitor: the
.exeis the main button. Linux visitor: the Linux assets. macOS: what exists for macOS, or "not available yet". Another OS's file is never the main button. - Linux: three labelled buttons. "Ubuntu / Debian (.deb)", "Fedora / RHEL (.rpm)", "Other Linux (AppImage)". If the browser hints at the distro (some user agents say Ubuntu or Fedora), that one can be first, but all three stay visible.
- A package kind on assets. Either inferred from the extension (
.deb,.rpm,.AppImage,.exe,.msi,.dmg), or a new optional--kindonrelease upload, returned inrelease assetsand the release JSON, so the card and any updater can tell them apart. - "All downloads". A small link under the buttons listing every asset of the version with its platform, arch, size and sha256.
- Optional: a stable "latest" URL per kind. For example
/download/adom/hydrogen/latest/debredirects to the newest .deb. It lets a one-line Linux installer script on the page always fetch the newest build.
Why it matters beyond Hydrogen. Adom Bridge already has a Linux AppImage that has no place on its page, and any app shipping Linux packages will hit the same wall.
Happy to test it against a Hydrogen insiders release as soon as one has Linux assets.