Moorhold docs

Each release of Moorhold is published at https://get.moorhold.dev/<version>/. One signature, on the release lock, covers everything a server runs. This page lists the files, what's in each and how each is checked. It describes the files of the latest release (2026.11.4).

File What it is How it's checked
install.sh The installer for this release. See the installer reference. Its sha256 is in SHA256SUMS and pinned in each cloud-init file. It carries the release key and checks everything else.
release.lock What the release is made of: the versions and sha256s below. Its minisign signature, release.lock.minisig.
release.lock.minisig The minisign signature over the whole lock. Against the release key.
moorhold-<version>.tar.gz The Moorhold bundle: the CLI, the portal and everything the server runs from it. Its sha256, pinned in the signed lock.
manifest.yaml The supported-versions manifest: every tool, its version, its images and their digests, licences and credits. Its sha256, pinned in the signed lock.
cloud-init-hetzner.yaml, cloud-init-ionos.yaml Cloud-init that installs this release on a new Hetzner or IONOS server. Each pins the installer's sha256 and checks it before running it.
SHA256SUMS The sha256 of the installer, the lock, the bundle, the manifest and the cloud-init files, for people who check by hand. It isn't signed. Check the lock's signature for that.

Node comes from nodejs.org, pinned by sha256 in the lock. The tools' images come from their registries and Moorhold's own images from registry.moorhold.dev, each pulled by the digest in the manifest, never by tag. Pulling Moorhold's images on a server needs your access key. The Moorhold app for Mac needs none.

File What it is
https://get.moorhold.dev/LATEST The latest release's version number, and nothing else.
https://get.moorhold.dev/moorhold-release.pub The minisign public key releases are signed with, key id 7F6D12F3F6217F9C. The installer carries the same key.

Your server asks get.moorhold.dev for the latest version number. It sends no data, but our site sees your server's address.

It checks only when an admin asks: once a day while the Updates page's daily check is on, or when someone presses Check for updates. It fetches LATEST, then that release's release.lock, its signature and its manifest.yaml, and offers the release only if the lock's signature verifies and the manifest matches the sha256 the lock pins.

moorhold-release 1
version <version>
registry registry.moorhold.dev
node x86_64 <url> <sha256>
node aarch64 <url> <sha256>
bundle <url> <sha256>
manifest <url> <sha256>
Line What it is
moorhold-release 1 The lock's format. The installer refuses a lock in another.
version The release. The installer refuses a lock for another release.
registry Where Moorhold's own images are pulled from.
node The processor, the Node download and its sha256. The latest release has a line for x86_64 and one for aarch64. The aarch64 one is for the Moorhold app for Mac. Locks before 2026.11.2 have x86_64 only.
bundle The Moorhold bundle and its sha256.
manifest The manifest and its sha256. Locks from 2026.10.6 on have it.

An ARM (aarch64) server isn't supported: the installer stops on one after it has checked the lock's signature.

  1. The installer carries the release key. When you download it yourself, check its sha256 against SHA256SUMS, or against the value in the install guide or the cloud-init file.
  2. The installer downloads release.lock and its signature and checks the signature with the key it carries. It stops if the signature doesn't verify.
  3. It downloads Node and the bundle and checks each against the sha256 the lock pins. It stops on a mismatch.
  4. The bundle's moorhold install pulls every image by the digest in the manifest.
  5. The installer keeps its key in /etc/moorhold/release.pub. sudo moorhold upgrade <version> and --check check the next release's lock with that key before anything else.

A signature that doesn't verify, or a file that doesn't match, stops the install with a message to stop and tell hello@moorhold.dev. An upgrade stops before it changes anything.

You need curl, sha256sum and minisign. On Ubuntu or Debian, sudo apt install minisign installs minisign. These commands check the latest release, 2026.11.4. For another release, use its version, and the install.sh line from that release's SHA256SUMS. That file isn't signed, so its line only catches a broken download. The signature check is what shows the release is ours.

First check the installer against its sha256:

Terminal window
curl -fsSLO https://get.moorhold.dev/2026.11.4/install.sh
echo '31575b713ddee80dd36de3e5f1bb5e93da36a34f066ba145212ed37bf4ec6618 install.sh' | sha256sum -c -

It must print install.sh: OK. If it doesn't, stop.

Then check the lock's signature against the release key, key id 7F6D12F3F6217F9C. The key is written into the command, so a forged lock from a forged server can't pass:

Terminal window
curl -fsSLO https://get.moorhold.dev/2026.11.4/release.lock
curl -fsSLO https://get.moorhold.dev/2026.11.4/release.lock.minisig
minisign -V -P RWScfyH28xJtf1DCwDTYUUS3wlSzmrKr2426mvg+EfqIV+mqziD5q5Si -m release.lock

It must print Signature and comment signature verified. If it doesn't, stop. The same key is published at https://get.moorhold.dev/moorhold-release.pub.

Then check a file against the sha256 the lock pins, for example the bundle:

Terminal window
curl -fsSLO https://get.moorhold.dev/2026.11.4/moorhold-2026.11.4.tar.gz
grep '^bundle ' release.lock
sha256sum moorhold-2026.11.4.tar.gz

The two sha256s must be the same.

From 2026.10.7, the published manifest.yaml has spec.upgrade, copied from the release notes. The portal's Updates page and sudo moorhold upgrade read it.

Field What it is
type normal, needs-action or security-fix. A security-fix release fixes a security problem in Moorhold.
summary The release notes' one-line summary.
downtime How long Moorhold is unavailable while it updates, as the release notes say.
from The lowest running release that may upgrade straight to this one. Older ones go through it.
needsApproval true when a person must approve the update, because it has breaking changes or manual steps.
manualSteps What you do by hand, in order. A release with manual steps needs approval.

spec.portal.mcpRevisions lists the MCP protocol revisions the portal's MCP server speaks, newest first.

A release can be marked skipped after it's published, when servers shouldn't update to it. Its files stay on get.moorhold.dev. The Updates page offers the release to use in its place.