inference-bot
48c4827957
The previous sheet's record counts could not be reproduced and at least two listed records did not exist, so it was replaced rather than corrected. Rebuilt from a screenshot of the domains.coop panel: 11 records total, of which two are wildcards carrying both A and AAAA. That is the item the old sheet omitted, and it is the one that matters most — every application hostname (chat, portal, panel, dashboard, newsletter, gateway, vault, git, registry, files, forum, email, docs, my, status) resolves ONLY via the wildcard and is not an individual record. A cutover that moves the apex but not the wildcards leaves all of them behind. Also recorded: the second DKIM selector (UUID-named, 2048-bit) that is almost certainly Scaleway TEM's, and which explains why probing plausible selector names never found it; the absence of any CNAME, CAA, SRV or ACME records; an unexplained server.inference.coop A record that must be identified before it is moved; and the pre-window TTL reduction. Known gap: row 11's full name and value are truncated in the panel screenshot and must be read in the panel before that row is edited.
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.