benjamin
20e8eb1874
Squashed history rewrite: earlier revisions of the docs carried private hostnames; placeholders throughout history now. - Fix phone remote threading (welcome/get_state/broadcast) — remote connects and mirrors channels, Now/Next, favorites - Phone-first onboarding (ADR-0007): one QR, server URL + IdP login on the phone (closes #11) - Ten-foot settings + Erweitert sub-screen (closes #14), TvTextField D-pad focus fix (closes #9) - EPG grid envelope parsing, Now/Next live (closes #10) - Self-healing error states (closes #13), in-app updater (closes #12) - Channel group filter chips fed by Dispatcharr groups Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
976 B
status
| status |
|---|
| accepted |
Domain split: nodecast as family viewer, Dispatcharr as engine
The family needs comfortable SSO viewing in the browser; Dispatcharr's web UI is an admin surface, not a viewer. We reinstated nodecast-tv as the browser frontend on (it already has an OIDC login and in-browser transcoding) — but demoted to a pure viewer with exactly one source: Dispatcharr's M3U/EPG output. Dispatcharr stays the engine (sources, aggregation, failover, per-user favorites for the TV app) and moved to (internal admin) plus api. (external API for Castarr sticks outside the LAN; the OIDC redirect URI is derived from the request host, all three hosts are registered at the IdP).
Access control lives on the IdP, not in app code: an Authentik group policy
binding (adult) on the nodecast, Dispatcharr and Castarr applications gates
both browser login and the device flow. The fork's OIDC_REQUIRED_GROUP knob
stays unused.