Skip to content
Skip to this exploration
All explorations

Practical self-hosting · beginner

01 · What are you actually taking home?

Define a service promise before installing a homelab.

10 min 5 sectionsv1

What you can take away

  • Write a service promise with boundaries and a recovery target.
  • Write a six-line service card for a disposable practice radio: audience, essential function, acceptable outage, acceptable data loss, recovery owner, and one feature you would deliberately disable during an incident

Your trail through this idea

Checking saved progress…

Imagine that a family member wants to listen to the radio while its creator is away. Which parts of the system have to keep working? Ian’s history of a self-hosted radio and local AI makes this a useful starting question: the interesting artifact is a service people can use, not a list of containers.

Prerequisite: none; bring a notebook and a willingness to mark unknowns.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

An operator owns several promises at once: availability, data care, access, updates, and recovery. A working demonstration proves only that one path worked once. A service promise describes who depends on it, what they can reasonably expect, and what happens when it fails. These are design choices you can test before buying hardware.

The early web offers a useful counterweight to an elaborate stack. CERN preserves the first website, including a route to a line-mode browser experience. Its educational value here is the separation of an understandable information service from the machinery used to deliver it. Adding an AI narrator, identity provider, and music catalog adds dependencies; each should earn its place.

Checking saved progress…

Work through the case

Consider an original design exercise: a radio can continue playing approved local tracks even when its AI narration service is unavailable. Draw two paths: audio delivery and optional narration. Put identity, storage, network access, and scheduling on whichever path actually needs them. A shared dependency belongs on both paths. Do not assume the current Rassys deployment already behaves this way.

Checking saved progress…

Make something useful

Try this

Original exercise

Write a six-line service card for a disposable practice radio: audience, essential function, acceptable outage, acceptable data loss, recovery owner, and one feature you would deliberately disable during an incident. Ask someone to read it and describe the promise back to you. Revise any sentence they interpret differently. This is an original planning lab; it changes no live services.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

What makes a service promise testable?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

The result should tell a future operator what matters first. If every feature is essential, simplify the promise until there is a useful degraded mode. Keep this card: the recovery capstone will test it.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations