Hosted forges in the nightly backup

Each forge this one hosts goes into the nightly snapshot (#13819), under children/<name>/.

WhatWhere in the snapshot
Database (a consistent copy, taken while it runs)forge.db
Repositoriesrepos/<owner>/<name>.bundle
SSH host keysssh/
Its key, wrapped under FORGE_SNAPSHOT_PASSPHRASEsecret.key.wrapped (without a passphrase the key stays home)
Every app's production dataalongside
This forge's own record of itledger.json

Chunks are shared with the rest of the snapshot, so a forge unchanged since last night sends nothing. A forge that cannot be read is named in the manifest's hosted list and the log; the snapshot goes on without it.

Read from inside the forge's directory only

A hosted forge's directory is the forge's own to write, and its host reads it for the snapshot from outside the forge's cell (copyHosted, src/snapshot/hosted.ts). So the copy stays inside it:

Where it shows

Restore one forge

Into an empty data directory; children/<bodyId>/ and spawn/<name>.json are written there:

bun run src/snapshot/restore.ts latest <data-dir> --forge <name>

A whole restore of the parent leaves children/ out; restore each forge this way.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs