ReaperOfVeriod/trixy-linux-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: describe client auth development behavior

Browse Source
This commit is contained in:
ReaperOfVeriod
2026-10-25 04:24:11 +01:00
parent 9ea2899ca7
commit 8c8d632557
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6
View File
@@ -2,6 +2,12 @@
This directory is the home of the standalone Linux client repository. This directory is the home of the standalone Linux client repository.
The current development shell connects to the server readiness endpoint and
provides an administrator login gate. The browser/dev client keeps its bearer
session in memory only; the native AppImage integration must replace that
temporary behavior with the Linux kernel keyring before persistent client
authentication is considered complete.
The client is a Svelte-based control surface distributed as an x86-64 AppImage. It communicates with `trixie-server` through the documented versioned HTTP and authenticated WebSocket interfaces. The client is a Svelte-based control surface distributed as an x86-64 AppImage. It communicates with `trixie-server` through the documented versioned HTTP and authenticated WebSocket interfaces.
Implementation has not started. See the parent workspace's `PLAN.md`, `TODO.md`, and `AGENTS.md` before beginning work. Implementation has not started. See the parent workspace's `PLAN.md`, `TODO.md`, and `AGENTS.md` before beginning work.