Flatpak repository for Zathu Software, served at https://flatpak.zathu.net/ and listed in KDE Discover / GNOME
Software once a user adds https://flatpak.zathu.net/zathu.flatpakrepo. The user-facing page is
https://zathu.net/flatpak/.
The OSTree repo is not stored in git. Each publish run mirrors the live Pages site, imports the new bundles, signs, prunes (keeps 3 commits per ref), and redeploys. The git repo holds only this tooling.
gpg --quick-generate-key "Zathu Software Flatpak <flatpak@zathu.net>" ed25519 sign never
gpg --list-secret-keys --keyid-format long # note the key id
gpg --armor --export-secret-keys <KEYID> # -> secret FLATPAK_GPG_PRIVATE_KEY
Back the private key up somewhere safe. Losing it means every user has to re-add the remote.
cgarst/zathu-flatpak, push this directory.flatpak.zathu.net; enforce HTTPS.
Secret FLATPAK_GPG_PRIVATE_KEY; variable FLATPAK_GPG_KEY_ID.CNAME flatpak -> cgarst.github.io.repository_dispatch on this repo (Contents: read/write on
cgarst/zathu-flatpak) to each publishing project as secret FLATPAK_REPO_TOKEN.After the project’s release job has uploaded its *.flatpak files to a GitHub release:
- name: Publish to the Zathu Flatpak repo
env:
GH_TOKEN: $
run: |
gh api repos/cgarst/zathu-flatpak/dispatches -f event_type=publish-flatpak \
-f 'client_payload[source_repo]=$' \
-f 'client_payload[tag]=$'
Or run the workflow by hand from the Actions tab. New projects must be added to the allowlist in publish.yml.
master, the flatpak-builder default).
The .flatpakref templates assume that.RuntimeRepo in the .flatpakrepo makes Flatpak add it if missing.