You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Architecture] Split Libation into a headless service (libationd) + thin multi-frontend clients #2178
Part of a set of [Architecture] proposals for the next major architecture step.
Goals
Headless batching without a display server: Run scans/liberations in Docker/servers without X11/VNC/GTK3/WebKitGTK.
Simultaneous CLI + GUI: Allow CLI and GUI to operate on the same library at the same time without racing on SQLite, Lucene, or AccountsSettings.json.
Decouple Audible compatibility from C# UI framework churn: Allow alternative frontends (including a lightweight Web UI or frontends in other languages).
Vision-impaired accessibility: Make it practical to offer a first-class accessible frontend (e.g., semantic HTML + ARIA Web UI for NVDA/JAWS/VoiceOver/Orca, or a thin native/TUI client) without maintaining LibationWinForms forever or duplicating Audible/DB logic.
Proposal
Move toward a stateful headless backend (libationd) that owns the DB, auth tokens, download/decrypt queue, and file placement, exposing a local HTTP/JSON + SSE/WebSocket API (over localhost or Unix socket with a per-user token):
Desktop ("in-process-or-attach"): Launching desktop Libation auto-starts libationd (or attaches to one already running), so normal desktop users see zero daemon-management complexity while libationcli can talk to the same live instance concurrently.
Server / Docker:libationd runs headless and can serve a static Web UI directly, eliminating VNC/KasmVNC overhead.
Activity