Homelab Academy / Modules
Orient, prior check, guided practice, required Feynman, reflect.
Module: Requests & Media Servers
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Describe Bazarr's role in a media automation architecture
Bloom level: Understand / Apply
Last reviewed: 2025-03-08
Describe Bazarr's role in a media automation architecture
Explain how Bazarr integrates with Sonarr, Radarr, media storage, and subtitle providers, then build and validate a least-privilege deployment manifest without starting containers or changing an existing media stack.
Complete the module reading first:
Explain Bazarr to a peer as a subtitle librarian that depends on two kinds of access. Sonarr and Radarr tell it which movies and episodes exist, which are monitored, and where their files should be. Filesystem mounts let it inspect those files and place matching subtitle sidecars beside them. If the API works but the paths do not match, Bazarr knows about a title but cannot reach its file. If the paths work but permissions are read-only, Bazarr can inspect the library but cannot save subtitles. Language profiles define what the household wants, providers offer candidates, and scoring helps avoid weak matches. A safe rollout begins with narrow permissions, consistent paths, one profile, one provider, and a small test set.
Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.