Skip to content

v0.2.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Nov 18:57
· 1 commit to main since this release
v0.2.0
This tag was signed with the committer’s verified signature.
fuseraft Scott Stauffer
SSH Key Fingerprint: /zP5XLMEx/qWhxfToicWTSgWndvcURxDyAB5mH2A2O8
Verified
Learn about vigilant mode.
c241456
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The Daemons page can now be relied on for a fuseraft serve on another machine. It stays connected, picks work back up after either side restarts, can be shared with non-admins, and keeps its secrets encrypted. It needs fuseraft v1.14.0 on the daemon's machine for reconnecting, restarts and wss://.

New

  • Stays connected. Daemons connect when the server starts and reconnect after a dropped connection, with backoff. A wrong token, an untrusted certificate or a protocol mismatch stops the retries and shows why.
  • Picks work back up. After a network drop, a restart of fuseraft-web or a restart of the daemon, a running task carries on, its pending approval is asked again, and results that finished meanwhile appear.
  • Saved daemons. Daemons added on the page are kept in <data>/daemons.json (mode 600), with their tokens encrypted, and stay connected or disconnected as you left them.
  • TLS. CertificateSha256, also a field on the page, trusts a self-signed wss:// certificate by its fingerprint. A plain ws:// URL to another machine is marked unencrypted.
  • Sharing. Admins can share a daemon with named users, via "Users": [...] in Fuseraft:Daemons or a field on the page. Those users see only their own tasks and approvals; everyone else doesn't see the daemon at all.
  • Read-only daemons. A daemon reached with a read token from its --tokens-file shows its progress, marked read-only, with no task box.
  • Encrypted keys. Fuseraft:KeyCertificate (an RSA .pfx, password in FUSERAFT_WEB_KEY_CERT_PASSWORD) encrypts the data-protection keys. On Windows they're encrypted with DPAPI by default. See docs/deploying.md.

Fixed

  • Approval cards on the Daemons page didn't appear until some later event refreshed the page.

Heads-up: a daemon older than fuseraft v1.14.0 still works, but the page warns that a dropped connection there loses the pending approval. Back up the data directory's daemons.json along with keys/, and the key certificate if you set one: without the keys, saved daemon tokens can't be read.

What's Changed

  • docs: point at the renamed repo and require fuseraft v1.13.0 by @fuseraft in #6
  • feat(daemons): keep remote daemons connected, shared and safe across restarts by @fuseraft in #7

Full Changelog: v0.1.0...v0.2.0

Contributors

fuseraft
Assets 7
Loading