[Feature]: Desktop app: release packaging (tarball, AppImage)

Offen
#96 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
24/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, linux, rust
Bereich
desktop, release

Rechercherichtung

Read the epic #80 first, then the dependencies #81 and #85 and the existing release workflow in release.yml. Check licenses/collect.sh and the desktop workspace packaging inputs described here. Done means a test tag publishes both Linux artifacts, the AppImage runs on the listed distributions, URL handling works, and a branch build is available to the NVIDIA tester.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a planning session with @PhrolovaMoe. Part of #80, builds on #81 and #85. Read the epic first.

Area

Desktop app

Problem

People need to install the app, and NVIDIA testers need binaries well before the first release, because David's machine is AMD.

Proposed solution
Release artifacts

A desktop job in release.yml (x86_64-unknown-linux-gnu, ubuntu-24.04, GitHub-hosted, glibc), built from the same tag as the server, with --locked:

  • Tarball tinystream-desktop-<version>-x86_64-linux.tar.gz:
    • tinystream-desktop (the binary);
    • dev.tinystream.app.desktop (with MimeType=x-scheme-handler/tinystream;);
    • hicolor icons from assets/logos, at the usual sizes plus scalable;
    • an AppStream dev.tinystream.app.metainfo.xml;
    • LICENSE, README.md, THIRD_PARTY_LICENSES;
    • an install.sh that copies all of that into ~/.local (or a prefix) and runs update-desktop-database.
  • AppImage tinystream-desktop-<version>-x86_64.AppImage, from the same files. The packaging tool (appimagetool or similar) is downloaded at a pinned version and checked against a pinned SHA-256 in the workflow. No unpinned downloads.
  • THIRD_PARTY_LICENSES comes from licenses/collect.sh, extended to take the desktop workspace: its crates (cargo-about over desktop/Cargo.lock), the native stack including mpv/libplacebo/nv-codec-headers (#85), Geist and Lucide.
  • The publish job attaches both to the release, next to the server archives and the APK.
  • aarch64 Linux is left out until there's hardware to test it on.
Dynamic dependencies

Check the final binary with ldd/readelf -d in CI, against an allowlist of libraries every desktop Linux has (glibc, libm, libstdc++, libEGL/libGL, libvulkan, wayland-client/egl/cursor, libxkbcommon, libX11 family, libasound, D-Bus if not pure Rust). Things loaded at runtime (libcuda, libva drivers, PipeWire/Pulse where mpv loads them) aren't in the list. Fail the job on anything else.

Test builds

A workflow_dispatch (and push to feat/desktop) build that uploads the tarball and AppImage as workflow artifacts, so testers can try a branch without a release. It needs no secrets.

Done when

A release from a test tag has both artifacts. The AppImage runs on a clean Ubuntu 24.04, Fedora and Arch (and David's Void). install.sh registers the URL scheme, so xdg-open tinystream://… opens the app. The NVIDIA tester runs a branch build.

Vorherrschende Sprache
TypeScript
Sterne
4
Forks
1
Ø Merge
4 Std. 49 Min.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Keine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus tinystream-dev/tinystream

Alle Issues in tinystream-dev/tinystream

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.