Runbooks

Operational runbooks for the co-op's infrastructure, published so members can read them and raise problems. That review is the point: these plans are safer when more eyes have been over them before anything irreversible happens.

Comment, or open an issue. There is no separate private copy — this repository is the source.

Contents

• cloudron-server-migration.md — the plan for moving Cloudron to the new server: pre-flight, the cutover window, what must be in hand first, and how to verify a restore. The one to read if you want to find problems.
• dns-change-sheet.md — the record-by-record cutover sheet.
• migration-before-state.json — the captured pre-migration state that the restore checker compares against.
• provider-pricing/ — what our model providers charge, and when it changed.

Read the DNS sheet with this in mind

Its record counts cannot be trusted until reconciled against the registrar's panel. The zone is wildcarded, so any hostname resolves — a name that answers proves nothing about whether a record exists. At least two listed records turned out not to exist, and the real record inventory is only visible in the registrar's own list.

No secrets here

Audited 2026-11-01, including the full commit history: no credentials, tokens, keys, member emails or account identifiers. Where a runbook needs a credential to exist (a backup passphrase, an S3 key), it records where the credential is held, never the credential.

Completed

• cloudron-server-migration.md — the move to Infomaniak, completed 2026-11-02. Kept as the record of how it was planned and done; current operational procedure now lives in the co-op's cloudron-ops skill and current member-facing description in co-op/docs/infrastructure.md.