feat: package the app as a flatpak
This commit is contained in:
parent
8e9d2a92a6
commit
080b47b24f
11 changed files with 135 additions and 1 deletions
15
README.md
15
README.md
|
|
@ -38,3 +38,18 @@ The tests run offline against an in-memory store: seed and key parsing, a sealed
|
|||
## Status
|
||||
|
||||
Work in progress: the UI is unexercised against a live server — the store, crypto and address paths are covered by tests, the network flows (register, fetch, send, rotate) are wired to fumi-core's operations but only smoke-tested as far as launching the window.
|
||||
|
||||
## Packaging
|
||||
|
||||
`devbox run package` builds and installs the app as a Flatpak from
|
||||
`com.randogoth.carrier.json` — the binary, the desktop file, the metainfo and
|
||||
the icon all come from the repo, and the tooling (`flatpak`, `flatpak-builder`,
|
||||
`appstreamcli`) lives in the devbox environment. The flatpak runtime is the one
|
||||
dependency outside devbox; install it once:
|
||||
|
||||
flatpak install --user flathub org.gnome.Sdk//51 org.freedesktop.Sdk.Extension.rust-stable//26.08
|
||||
|
||||
The result is installed into the user flatpak and runs as
|
||||
`flatpak run com.randogoth.carrier`. Inside the sandbox the app keeps its
|
||||
config under `~/.var/app/com.randogoth.carrier/config/carrier`, so a flatpak
|
||||
install starts with a fresh identity rather than the dev build's account.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue