Cutting a domain over (#648)

Move an app's domain from the platform to the forge app, checked first, with a receipt, and undone in one step. It is the last line of the migration checklist (docs/features/migration-mode.md).

The path

  1. Verify the domain on the app (docs/features/platform-app-move.md) and tick every line of

MIGRATION.md: the app must be at parity.

  1. Check at /<owner>/<name>/cut-over (or c on the terminal screen). The same paths asked of the

platform and of the forge app must answer with the same status codes (src/apps/parity_probe.ts). Check changes nothing.

  1. Cut over (o in the terminal). The name is pointed at the app: a registrar edit when the

repository holds the secret DNS_API_TOKEN, else the receipt names the one record to publish. The records the name carried are kept with the domain. The receipt says what changed and the certificate's state. The platform app keeps running, unrouted.

  1. Undo (u) puts the kept records back and forgets the cut-over. With nothing kept a cut-over

is refused ("no way back"): keep the old records first, or set DNS_API_TOKEN.

Admins of the repository only, like every domain action. The terminal door is src/tui/screens/cutover.ts, a palette command while an administered repository is open. Events: app.domain.cut_over, app.domain.cut_undone.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs