Changelog

v0.13.0

Repoint DNS records + clone-wizard back navigation · July 3, 2026

The DNS module learns the migration's final move — repointing the record itself — and the clone wizard lets you step back a screen instead of being locked forward.

Highlights

  • Repoint a DNS record (p). In the DNS view (n/N), alongside ⏎ edit TTL, p opens "Point at…" — pick one of your SpinupWP servers from a list (name + IP, the record's current home tagged) or enter a custom IP, confirm, and the record moves. Route 53 changes keep applying in the background after you close the editor, and the row shows → new IP while they do. A Cloudflare proxied record repoints its origin behind the proxy; CNAMEs explain that they follow their target instead. It's the clone wizard's DNS cutover as a standalone action — migrate a single site, finish a cutover by hand, or fix a stale record.
  • Go back in the clone wizard (← / h). The setup steps (Plan ↔ Destination ↔ Connect dest ↔ Git access) step back freely. Once cloning has started, the one back edge is DNS cutover → the clone roster, so you can re-run a verify or retry a failed site before flipping live traffic — records already checked, flipped, or mid-flight are never reset by the round trip.
  • Vanity sites for busy servers (V). Previously only offered on empty servers; now offered on any server that doesn't yet have a site at its own hostname, surfaced as a V row under Manage in the server's Details panel. Busy boxes get the same hostname status page and key-holding site user.

Fixed

  • ◀ here markers are now always relative to the server you're viewing. After checking DNS on a migration's destination server, reopening the view on the old server showed records pointing at the new box flagged as "here" (with a wrong "N point here" tally) — the flag was baked into the hostname cache at lookup time. Resolved IPs are now cached neutrally and "here" is computed against the current server; a just-repointed record reads correctly immediately.
  • Clone verification no longer reports a cut-off read as a mismatch. If the wp-cli facts script was interrupted partway (a timeout, or a plugin stalling on an outbound call), the missing tail rendered as – mismatch rows that read as "the clone differs." The read now runs with --skip-plugins --skip-themes, gets a bigger budget, and an incomplete read fails loudly naming the side instead.

View on GitHub →