Blame
|
1 | # Streaming service |
||||||
| 2 | ||||||||
| 3 | This system is a fully automated media acquisition and organization stack designed to manage movies and TV shows end-to-end with minimal manual intervention. |
|||||||
| 4 | ||||||||
| 5 | At its core, the stack combines four services: Radarr for movies, Sonarr for TV series, Prowlarr for indexers, and qBittorrent for downloading content. These are optionally fronted by Jellyseerr, which provides a user-friendly request interface. |
|||||||
| 6 | ||||||||
| 7 | All services share a unified filesystem layout based on /data, separating temporary downloads from final media libraries. Downloads are processed in /data/downloads and then automatically imported into structured libraries (/data/movies and /data/series) used by a media server such as Jellyfin. |
|||||||
| 8 | ||||||||
| 9 | The system operates in a fully automated pipeline: |
|||||||
| 10 | ||||||||
| 11 | 1. A request is submitted (optional via Jellyseerr) |
|||||||
| 12 | 2. Radarr/Sonarr query indexers through Prowlarr |
|||||||
| 13 | 3. qBittorrent downloads the selected release into category-based folders |
|||||||
| 14 | 4. Radarr/Sonarr import and organize the media into the final library structure |
|||||||
| 15 | ||||||||
| 16 | Consistency across containers is enforced through a shared UID/GID (1000:1000) and strict separation between configuration (/config) and media data (/data). |
|||||||
| 17 | ||||||||
| 18 | This architecture prioritizes reproducibility, automation, and clean separation of concerns, ensuring that once configured, the system requires minimal ongoing maintenance while remaining scalable and predictable. |
|||||||
