Files
inference-bot 098b0e9caa runbooks: the migration is complete — mark it as history, not pending work
The cutover finished 2026-11-02 and this repo is public and read by members, so leaving a plan that reads like outstanding work is actively misleading. A dated banner now says it is complete and retained as the record; the STATE OF PLAY section is re-labelled as pre-cutover and marked superseded, with the one part known to be wrong (Listmonk's mail path, which moved to Scaleway TEM) named rather than silently corrected; and both files point at where live knowledge now lives — the cloudron-ops skill for procedure and co-op/docs/infrastructure.md for the member-facing description.
2026-11-02 15:37:28 +00:00

36 lines
1.9 KiB
Markdown

# 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](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](dns-change-sheet.md)** — the record-by-record cutover sheet.
- **[migration-before-state.json](migration-before-state.json)** — the captured pre-migration state
that the restore checker compares against.
- **[provider-pricing/](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](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`.