The first DNS write, plus a one-keystroke way to pull a production database into your local copy — all from the terminal.
Highlights
- Edit DNS record TTLs — the first DNS write. From the DNS migration view,
⏎on a site's hosting record opens a focused editor to change its TTL (preset or custom), written to AWS Route 53 or Cloudflare behind a confirm step. The prep step for a low-risk cutover: lower the TTL, repoint, restore. An edit-time check re-reads the live nameservers and blocks the write if your account's zone isn't the one actually serving the domain. Cloudflare proxied records are read-only. - DNS view is now a migration lens. Organized by site (labeled by its own domain, even subdomains), each with its hosting record's type / TTL (in seconds) / value, a
◀ hereflag when it points at this server, and a+wwwtag whenwwwfollows the apex.nscopes to one site;aexpands to the whole server. - Download a production DB backup (
d). On a linked WordPress site, export the production database withwp-cli, gzip it, and download it into the copy'ssql/folder — read-only on production, no local WP-CLI needed. - Pull production → local (
p, opt-in). Refresh your local database from production: backs up local first, imports, rewrites URLs (wp search-replace), and runs your existingbin/sync.d/post-import.shhook. Works with Standard WP and Bedrock with no per-site config. It overwrites your local DB, so it's off by default — enable withlocalSync. - Site Control panel. The Search action menu is now grouped (Open / Remote / Local / Server) so the growing per-site action set stays scannable.
Notes
- DNS edits only ever touch a site's own hosting records — your MX, TXT, and other zone records are never shown or modified.
- Editing a Cloudflare record needs a token scoped to
Zone.DNS:Edit(the read-onlyZone:Readtoken isn't enough). - The DB backup/sync actions appear only for WordPress sites that are linked to a local copy; the destructive sync additionally requires the
localSyncopt-in.