Skip to content
Skip to this exploration
All explorations

Practical self-hosting · intermediate

32 · Start again without your memory

Rehearse recovery using only documented inputs.

10 min 5 sectionsv1

What you can take away

  • Evaluate a clean-room recovery against the service promise.
  • Give the recovery packet to another learner, or act as a new operator after setting aside your notes

Your trail through this idea

Checking saved progress…

The original operator is unavailable. Another person has the release, backups, and recovery instructions. Can they restore the essential service without guessing what the author meant?

Prerequisite: complete the preceding lesson or bring its worksheet.

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

Understand the system

PostgreSQL’s backup overview distinguishes backup approaches with different properties. Your recovery plan must use the approach actually taken, together with its required software and files. The lesson sequence now connects inventory, configuration, identity, secrets, data, and release provenance into one test.

A clean-room rehearsal avoids hidden help from an already configured host. Use a separate environment and synthetic data. Define the restore destination before any command, and verify that it cannot overwrite production. A successful rehearsal should test a user task, not merely a running process list.

Checking saved progress…

Work through the case

Original capstone: restore a fictional three-document library and a three-track radio schedule. Reader can access approved material; Editor can prepare a draft; unauthenticated access cannot retrieve the draft; radio fallback works without model generation. The service card from lesson 1 determines the priority order and acceptable delay.

Checking saved progress…

Make something useful

Try this

Original exercise

Give the recovery packet to another learner, or act as a new operator after setting aside your notes. Record every undocumented assumption they encounter. Check data integrity, role boundaries, essential service behavior, and elapsed time. Stop on any ambiguous destination or missing recovery key. Roll back only the isolated test environment; retain the original backup.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

What is the central clean-room recovery test?

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

Success is a recovery report with evidence and a revised handbook. If the service fails, the rehearsal has still produced valuable information—provided the result is recorded as a failed test and the gap is addressed before relying on 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