1 Release 42 Tags

RSS Feed

• v3.10.0 0e26d99228

  Compare

  ui: add alpine local and github_alpine usage instructions (#116)

  unkin-agent released this 2026-08-12 20:53:23 +10:00

  Why

  The alpine local repo (a real apk repo with auto-generated per-arch APKINDEX) and the new github_alpine remote (metadata-only apk index synthesized from a GitHub repo's release .apk assets) shipped without any "How do I use this?" UI guidance, unlike deb/github_deb. This adds the matching client instructions so users can consume and publish to these repos.

  How

  • Extend case 'alpine': in UsageInstructions.tsx to branch on isLocal (mirroring rpm/deb):
    • LOCAL: "Add the apk repo" snippet appends ${url}/api/v1/local/<name> to /etc/apk/repositories with apk update/add --allow-untrusted (served unsigned, parity with rpm gpgcheck=0), plus a "Publish a .apk" snippet uploading to the canonical <arch>/<name>-<version>.apk path (APKINDEX carries no filename, so path must match or install 404s).
    • REMOTE: existing caching-proxy snippet kept unchanged.
  • Add case 'github_alpine': (always remote-class): "Add the apk repo (metadata-only, from GitHub releases)" snippet with --allow-untrusted; note explains the per-arch APKINDEX is synthesized from release .apk assets and downloads redirect to the backing releases remote.
  • No other cases touched. npm run build (tsc typecheck + vite) passes; pre-commit passes.

  Reviewed-on: #116
  Co-authored-by: unkin-agent unkin-agent@unkin.net
  Co-committed-by: unkin-agent unkin-agent@unkin.net

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)