be-nj/castarr
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases 14 Wiki Activity

Bootstrap Castarr from NodeCast prototype

Browse Source 
Imported the native TV app (Kotlin, ExoPlayer, embedded remote server, QR
pairing) plus CONTEXT.md and ADRs 0001-0005. Rename, Compose for TV UI and
the Dispatcharr integration follow as tracked issues.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Benjamin
2026-08-25 00:09:00 +02:00
commit 6c5fee849e
44 changed files with 2418 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/adr/0003-dispatcharr-backend-via-standards.md Normal file
View File

@@ -0,0 +1,16 @@
---
status: accepted
supersedes: ADR-0001, ADR-0002
---
# Dispatcharr as backend, app speaks Xtream API + XMLTV
ADR-0001 made the app a companion to nodecast-tv; grilling the ecosystem
(Dispatcharr, Threadfin, Tunarr, ErsatzTV) showed they all emit standard
outputs, while nodecast-tv is the only backend with a proprietary API. We
decided to drop nodecast-tv and use Dispatcharr as the backend: it owns
sources, aggregation, failover, EPG and stream profiles. The TV app talks the
Xtream API (channels, categories, EPG as JSON) plus XMLTV, with a generic
M3U/XMLTV fallback so Threadfin/Tunarr/ErsatzTV work too. The nodecast-tv
fork plans (device tokens, ADR-0002) are void; the app-side M3U parser stays
as the fallback path.