Files and services on the server
On this page
This page lists where Moorhold keeps its files on an installed server, and the systemd units it
adds. It describes the latest release (2026.11.4). Don't edit these files by hand,
except stack.yaml, which sudo moorhold apply applies.
/opt/moorhold
Section titled "/opt/moorhold"Readable by root only.
| Path | What it is |
|---|---|
/opt/moorhold/releases/<version> |
One release: its own Node, the Moorhold bundle, and the signed release lock it was installed from. An upgrade unpacks the new release beside the running one. |
/opt/moorhold/current |
A link to the release that runs. An upgrade moves it only once the new release is up. |
/opt/moorhold/stack/stack.yaml |
Your Stack. See the Stack resource reference. |
/opt/moorhold/project |
The Docker Compose project rendered from the Stack. Moorhold writes it again on every start and upgrade. |
/opt/moorhold/code |
Extractor code for your web services, mounted read-only on Airflow's scheduler. |
/etc/moorhold
Section titled "/etc/moorhold"| Path | What it is |
|---|---|
/etc/moorhold/release.pub |
The release key the server trusts. sudo moorhold upgrade checks each upgrade with it. Mode 0644. |
/etc/moorhold/secrets |
Every secret the installer generated, one file each, readable by root only. Nothing Moorhold prints holds one. |
/etc/moorhold/secrets/MOORHOLD_SETUP_CODE |
The one-time setup code for https://<hostname>/setup. |
/etc/moorhold/secrets/registry-access-key |
The access key the server keeps, for pulling images. sudo moorhold access-key set and forget change it. |
/var/lib/moorhold
Section titled "/var/lib/moorhold"| Path | What it is |
|---|---|
upgrades.log |
One line for each upgrade and rollback. Mode 0600. sudo moorhold status shows the last. |
rollback-point.json |
The rollback point the last upgrade took, which sudo moorhold rollback goes back to. |
update-requests/ |
Only on a server installed before 2026.11.3, where the portal used it for approved updates. Nothing uses it now, and the first update from 2026.11.3 or later removes it. |
host-requests/ |
Where the portal leaves an empty file when an admin approves a request, such as more memory for an app, or an update. |
host-requests.next |
When the next request approved for a later time is due. |
power-requests/ |
Where moorhold-wake leaves an empty file when a tool should sleep or wake. |
plan/ |
What the server last heard about its plan from account.moorhold.dev. |
automatic-update.json |
Set while an automatic update runs. |
The portal can only create empty files in the request directories, and the services that read them ignore what's in them. Each service checks the approval in Moorhold's store again before it acts.
/run/moorhold
Section titled "/run/moorhold"A tmpfs, emptied at every boot.
| Path | What it is |
|---|---|
/run/moorhold/secrets |
The secrets the stack's containers read, written by moorhold start at every boot. |
/run/moorhold/memory |
The memory samples behind the portal's warning near an app's limit. |
/run/moorhold/host-requests/values |
A secret typed in the portal, for a moment, on its way to the service that sets it. |
Others
Section titled "Others"| Path | What it is |
|---|---|
/usr/local/bin/moorhold |
The moorhold command: runs the CLI of the release in /opt/moorhold/current. Without root it says Run it with sudo: sudo moorhold <command>. |
/run/moorhold-install |
The installer's working directory, and where the cloud-init files put the access key. |
systemd units
Section titled "systemd units"All in /etc/systemd/system. The installer and every upgrade write them.
| Unit | What it does |
|---|---|
moorhold.service |
Runs moorhold start --profile <profile> at boot, after Docker and the network, and moorhold stop at shutdown. sudo moorhold start-at-boot writes it again. |
moorhold-update.path, moorhold-update.service |
Only on a server installed before 2026.11.3, where they installed approved updates. They stay in place for a rollback to that release, which needs them, and the first update from 2026.11.3 or later removes them. A server installed with 2026.11.3 never has them. |
moorhold-update.timer |
Opens the maintenance window for automatic updates, by starting moorhold-requests.service. It keeps its name from earlier releases. It's there only while automatic updates are on. |
moorhold-requests.path |
Starts moorhold-requests.service when host-requests/ isn't empty. |
moorhold-requests.service |
Runs moorhold requests run-due: checks each approved request again and does it, then installs approved updates. While an update installs, other approved requests wait. It writes no core dump, because it may hold a secret typed in the portal. |
moorhold-requests.timer |
Every five minutes, starts moorhold-requests-due.service, which runs moorhold requests run-due --if-due for requests approved for a later time. |
moorhold-memory.timer, moorhold-memory.service |
Samples the memory of the apps Moorhold sizes, from shortly after boot. |
moorhold-power.path, moorhold-power.service |
Starts or stops a tool that sleeps while idle, when moorhold-wake asks. sudo moorhold power setup turns them on. |
To keep automatic updates off on a server whatever the portal says:
sudo systemctl mask moorhold-update.timer