CLASSROOM // HOMELAB ACADEMY M9 LESSON
M9 LESSONlesson

Homelab Academy / Modules

Teach it back 01-arr-stack-data-architecture-and-the: Lesson

Orient, prior check, guided practice, required Feynman, reflect.

Show commands for:
Class 34: ARR stack data architecture
Class 34 visual reference. Use it as the map, then prove it in the reading, lesson, and lab.

Overview

Module: ARR Data Model & Compose
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Explain why download and media paths should share one visible /data namespace.
Bloom level: Understand / Apply
Last reviewed: 2025-03-08

Objective

Learning objective

Explain why download and media paths should share one visible /data namespace.

Why it matters

Why this matters

Teach a predictable storage architecture for Sonarr, Radarr, download clients, and media servers by exposing one shared /data hierarchy. The lesson emphasizes consistent container paths, category separation, same-filesystem imports, atomic moves, hardlinks, identity alignment, and verification before deployment.

Learn

Learn

Complete the module reading first:

Teach it back

Feynman teach-back: required

prompt

Explain the /data model to a new administrator without using the words efficient, Docker, or magic.

model_explanation

The downloader and media organizer must agree on where a file lives. Both are given one shared cabinet called /data. Incoming torrent files go in one drawer, completed Usenet files go in another, and neatly named library files go in a media drawer. Because the drawers are in the same cabinet, the organizer can rename a file quickly or give the same stored file a second name. A torrent can therefore keep its original seeding name while the media library uses a clean title. Configuration files stay in a different cabinet because they contain application state and require a separate backup and security policy.

self_check_questions

Can you explain why /downloads in one application and /data/torrents in another creates operational complexity?
Can you explain why matching filenames do not prove that two files are hardlinks?
Can you state the two core requirements for a hardlink: the same filesystem and sufficient access?
Can you explain why application configuration and media data have different backup requirements?

Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.

Reflect

Reflection

  1. What did I learn?
  2. What did I struggle with?
  3. How does this connect to earlier classes?
Learn

Topic path (do in order)

Step Activity Purpose
1 Reading Learn
2 This lesson (Feynman) Explain
3 Lab Practice
4 Homework Apply
5 Quiz Test
← ReadingLab →