From ff62770bccdb89e7a58ecce7bb138df1fd60a382 Mon Sep 17 00:00:00 2001 From: "Foluso ADEBISI (DevBox Aux)" Date: Fri, 2 Oct 2026 11:26:35 +0100 Subject: [PATCH] docs(fpagent): document --tag and the upgrade path --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 25d0ffa..e01f818 100644 --- a/README.md +++ b/README.md @@ -163,8 +163,15 @@ libfprint, the udev rule, `plugdev` and the systemd service. On a field laptop: ```sh curl -fsSL https://tools.yrka.app/fpagent/install.sh | bash -s -- --enable-service curl -fsSL https://tools.yrka.app/fpagent/install.sh | bash -s -- --check # report only +curl -fsSL https://tools.yrka.app/fpagent/install.sh | bash -s -- --tag v1.0.0 --enable-service ``` +Rerunning it is the upgrade path: it installs the newest release (or `--tag` +for a pinned one), the bundle installer reports the version change, and with +`--enable-service` it restarts a running service so the new binary takes effect. +The version is the git hash carried in the asset name, stamped next to the +binary (`/usr/local/bin/fpagent.version`) and compared on the next run. + The forge is private, so the operator's laptop needs no credentials: the app reads the release with `GITEA_RELEASE_INSTALL_KEY` and proxies it through `/fpagent/releases/*`. Without that key the installer answers `503`.