ReaperOfVeriod 7aef4171af
Client checks / checks (push) Canceled after 0s
Client dependency and security checks / audit (push) Canceled after 0s
Preserve native sessions during temporary server outages
2026-10-25 17:51:10 +01:00
2026-10-25 06:53:53 +01:00
2026-10-25 05:43:49 +01:00
2026-10-25 05:49:25 +01:00
2026-10-25 03:52:37 +01:00
2026-10-25 06:57:31 +01:00
2026-10-25 03:52:37 +01:00
2026-10-25 03:45:43 +01:00
2026-10-25 06:53:53 +01:00
2026-10-25 03:52:37 +01:00
2026-10-25 03:52:37 +01:00

Trixie Linux Client

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/ crate defines the AppImage storage boundary: settings.json contains only the server address and username, while the session credential is stored in the Linux kernel keyring with no plaintext fallback.

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.

Connection recovery follows the server policy: the first retry is immediate, then retries wait 3, 10, and 15 seconds, followed by an indefinite 30-second interval until the server reconnects. Manual connection checks do not create overlapping retry loops.

The client currently includes the live dashboard shell, server connection and retry flow, administrator authentication, Twitch identity controls, chat and moderation surfaces, bot/overlay/plugin administration, and the native keyring storage boundary. Remaining live Twitch acceptance work is tracked in the parent workspace's TODO.md and operator checklist.

Consumes the versioned contracts from the sibling trixie-api repository.

S
Description
Trixie Linux client
Readme MIT
31 MiB
Languages
Svelte 79.7%
CSS 13.6%
Rust 5.4%
JavaScript 0.9%
TypeScript 0.2%
Other 0.2%