YOUreka/tools-legacy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(fpagent): document --tag and the upgrade path

Browse Source
This commit is contained in:
adebisi-fa
2026-10-02 11:26:35 +01:00
parent 2ad4aa63c6
commit ff62770bcc
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7
View File
@@ -163,8 +163,15 @@ libfprint, the udev rule, `plugdev` and the systemd service. On a field laptop:
```sh ```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 -- --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 -- --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 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 reads the release with `GITEA_RELEASE_INSTALL_KEY` and proxies it through
`/fpagent/releases/*`. Without that key the installer answers `503`. `/fpagent/releases/*`. Without that key the installer answers `503`.