Skip to content
Skip to this exploration
All explorations

Practical self-hosting · intermediate

31 · A release you can still install tomorrow

Make an artifact reproducible and verifiable.

10 min 5 sectionsv1

What you can take away

  • Build a release manifest and test its links and checksums.
  • Prepare a harmless text artifact and compute a SHA-256 checksum with your platform’s standard tool

Your trail through this idea

Checking saved progress…

Ian repeatedly reported missing or expired artifact links in earlier work. A deliverable is not complete because a message says it exists; someone must be able to retrieve and identify the intended bytes.

Prerequisite: complete the preceding lesson or bring its worksheet.

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

Understand the system

GitHub releases package a version with release notes and assets. Reproducibility also needs source revision, dependency locks, image identifiers where applicable, migration notes, and installation checks. A branch name can move. A checksum identifies bytes but does not establish who produced them or whether they are trustworthy.

Keep the artifact and its instructions consistent. A release that says 'run the validator' should include a working command for that exact source revision. The inspected source commit 3ece0dd13ce503a4fe80a53ffa2f960a9e54a7a1 contains a learning validator file while omitting its documented package-script aliases, a concrete reminder to test instructions as well as code.

Checking saved progress…

Work through the case

Original manifest: artifact filename, source commit, creation date, toolchain, checksum, module count, validation result, known limitations, and publication status. A private draft should say 'draft' and identify the review boundary. It should not imply that the live site already contains the files.

Checking saved progress…

Make something useful

Try this

Original exercise

Prepare a harmless text artifact and compute a SHA-256 checksum with your platform’s standard tool. Copy it to a second local filename, recompute, and compare. Then change one character and observe the mismatch. Keep the exercise in a new disposable directory. For a real release, test the delivered link using the intended access permissions before announcing success.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

What does a checksum establish by itself?

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 retrievable artifact with enough provenance to distinguish it from an older draft. An honest failed build or blocked link belongs in the release notes, not behind a completion claim.

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