Practical self-hosting · intermediate
33 · Build a service worth keeping
Connect technical choices to purpose, energy and maintenance.
What you can take away
- Choose a sustainable operating promise and retirement rule.
- Choose one service to keep, one to simplify, and one to retire in a fictional homelab
Your trail through this idea
Checking saved progress…
After thirty-two lessons, the next installation is not automatically the next improvement. Which service would you keep if maintenance time, power, and attention were all visible on the dashboard?
Prerequisite: complete the preceding lesson or bring its worksheet.
Understand the system
CERN’s first-website exhibit shows how much useful communication can begin with simple linked documents. Low-tech Magazine’s solar website deliberately makes energy constraints and possible downtime part of its design. These are different service promises, not universal templates for every application.
For a stranger excursion, RFC 1149 describes IP datagrams carried by birds. It is April Fools humor, not a production networking recommendation. Its playful premise makes a serious distinction memorable: moving a large amount of data eventually and answering an interactive request quickly are different achievements.
Work through the case
Original design challenge: choose between a continuously available family help page, an occasional batch photo index, and an experimental AI radio narrator. Give each a purpose, audience, energy/maintenance budget, and failure behavior. Some tasks can wait; others should have a simple always-available fallback. Complexity should follow the promise.
Make something useful
Try this
Original exercise
Choose one service to keep, one to simplify, and one to retire in a fictional homelab. Write a measurable reason for each decision. For retirement, include export, retention, access revocation, and a recovery window before data deletion. This is a planning lab; it authorizes no actual shutdown or removal.
Check your reasoning
A quick check · for your own learning
How should RFC 1149 be understood in this lesson?
A self-study prompt. You can retry; this is not an exam.
Keep the result and follow the sources
The final artifact is your own operating charter: what the homelab is for, what it will reliably do, and what it will decline to do. Curiosity and restraint can coexist. A system that remains understandable is easier to improve.
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.