Downloads page on the .com, from Gitea Releases #126

Open
opened 2026-11-07 16:42:25 +00:00 by rajames · 0 comments
Owner

What

A Downloads page on starshipos-f18.com, in the .com design, from which anyone can fetch a StarshipOS release -- served from Gitea Releases, not Nexus.

  • Where the files live: the repository is public, so a Gitea release's attachments download for anyone. release.yml gains a step: create the Gitea release for the tag and attach StarshipOS.iso (PC), raspi5.img.xz, MilkV.img.xz, SHA256SUMS and the documents (book, vol1-vol3, api). Nexus stays as it is (Maven coordinates, archive); its anonymous reads stay closed.
  • The page:
    • The latest release, marked plainly as an alpha while it is one
    • One card per board: PC -- the UEFI stick, written with Etcher or dd; Raspberry Pi 5 -- for Raspberry Pi Imager; Milk-V Mars -- and how to write it
    • Checksums, and the StarshipOS Root CA's fingerprint, so a download can be known to be ours (FABRIC-3.md XLVI)
    • Documents: the book, the three volumes, the API reference
    • "Try it first": the browser demo, once it is live (#115, #117)
    • Optionally, the nightly builds as "bleeding edge", with a warning
  • Linked from the .com's navigation; built and installed like the other pages (site/com/), designed first on the StarshipOS.com canvas.

Why -- the ruling or the design it comes from

Captain Bob, 2026-11-07: "Should we have a downloads page in .com?" -- "Yes", filed after the first alpha (v4.0.0-alpha.1), when there is a release to point at.

Done when

  • release.yml creates the Gitea release and attaches the images, SHA256SUMS and the documents
  • The page links to the latest release without being edited each time (check that Gitea 1.27 has a stable latest-asset link; otherwise the page reads the latest release from Gitea's API)
  • The Downloads artboard on the canvas, then site/com builds and installs it; in the .com navigation
  • Verified: as a guest, each link downloads the file it names, and its checksum matches SHA256SUMS

Area

site (the .com), CI (release.yml)

Priority

should

🤖 Filed with Claude Code

### What A **Downloads** page on starshipos-f18.com, in the .com design, from which anyone can fetch a StarshipOS release -- served from **Gitea Releases**, not Nexus. - **Where the files live:** the repository is public, so a Gitea release's attachments download for anyone. `release.yml` gains a step: create the Gitea release for the tag and attach `StarshipOS.iso` (PC), `raspi5.img.xz`, `MilkV.img.xz`, `SHA256SUMS` and the documents (book, vol1-vol3, api). Nexus stays as it is (Maven coordinates, archive); its anonymous reads stay closed. - **The page:** - The latest release, marked plainly as an alpha while it is one - One card per board: PC -- the UEFI stick, written with Etcher or `dd`; Raspberry Pi 5 -- for Raspberry Pi Imager; Milk-V Mars -- and how to write it - Checksums, and the **StarshipOS Root CA's fingerprint**, so a download can be known to be ours (FABRIC-3.md XLVI) - Documents: the book, the three volumes, the API reference - "Try it first": the browser demo, once it is live (#115, #117) - Optionally, the nightly builds as "bleeding edge", with a warning - Linked from the .com's navigation; built and installed like the other pages (`site/com/`), designed first on the StarshipOS.com canvas. ### Why -- the ruling or the design it comes from Captain Bob, 2026-11-07: "Should we have a downloads page in .com?" -- "Yes", filed after the first alpha (`v4.0.0-alpha.1`), when there is a release to point at. ### Done when - [ ] `release.yml` creates the Gitea release and attaches the images, `SHA256SUMS` and the documents - [ ] The page links to the latest release without being edited each time (check that Gitea 1.27 has a stable latest-asset link; otherwise the page reads the latest release from Gitea's API) - [ ] The Downloads artboard on the canvas, then `site/com` builds and installs it; in the .com navigation - [ ] Verified: as a guest, each link downloads the file it names, and its checksum matches `SHA256SUMS` ### Area site (the .com), CI (`release.yml`) ### Priority should 🤖 Filed with [Claude Code](https://claude.com/claude-code)
rajames added the
priority
should
kind
feature
status
backlog
labels 2026-11-07 16:42:25 +00:00
rajames added this to the v4.0.0-alpha.4 milestone 2026-11-07 20:16:10 +00:00
Sign in to join this conversation.