Changelog

v0.26.0

Clone a local working copy from production · August 26, 2026

Getting a site onto your machine used to be the one step SpinupTUI left you to do by hand. Now it's a keypress — or a command an agent can run.

Highlights

  • Clone a local working copy from production (L → c). On a site you have no copy of yet, L now offers a choice: e to type in a path you already have, or c to build the copy. It pulls the code down — git clone for git-deployed sites, rsync over SSH for the rest — runs composer install for Bedrock/Radicle, links the result, and hands off to the DB pull (p) and media fallback (m) you already know. Your local database and webserver config are never touched.
  • The same thing from the command line. spinuptui pull files <domain> [path] and spinuptui pull db <domain> --yes drive the identical engines with no TUI. Progress goes to stderr, the result to stdout — with --json, one object, exit code mirroring ok, and every failure carrying a stable reason plus a remedy naming the exact command that fixes it. Built so "pull that site down for local dev" can be handed to an agent.
  • --server <name> everywhere a domain is resolved (ssh, ssh-exec, both pull commands). A domain can legitimately live on two servers — a clone destination, a staging twin — and those sites were previously unreachable from the CLI: the ambiguity could be reported but never resolved. It now lists what matched and names the flag that picks one.
  • Search gets the full-width Control drawer from the Servers tab, instead of swapping its right-hand panel between Details and Actions. The Details pane stays put while you browse, and both views now share one control component, so they can't drift apart again.

Notes

  • A cloned copy needs its database credentials pointed at your machine before pull db will run, and the app now says so at the point it matters. The file pull brings the site's real wp-config.php down — production credentials and all — so local WP-CLI would otherwise authenticate as the production DB user and be denied. A Bedrock/Radicle clone has the opposite problem: .env isn't in the repo, so the checkout arrives without one. Both cases are flagged on the clone screen and again on a failed pull.
  • wp-content/uploads is deliberately skipped (that's what the media fallback is for), as are object-cache.php and advanced-cache.php — SpinupWP's Redis drop-in doesn't degrade quietly without Redis, it 500s on a cache miss.
  • The clone honors the layout rules the rest of the app does: it takes the site's whole files root, so a public/-style webroot brings wp-config.php down from the directory above it, and the real webroot is detected on the server rather than inferred from the public_folder setting.

Fixed

  • K (grant SSH key) and V (create/resume vanity site) now work on server results in Search, not just site results — both were advertised in the legend and silently did nothing.
  • A failed local-database backup no longer leaves a fake backup behind. The pre-import dump created its file before it could fail, leaving a bare .sql — empty, or worse, partial — sitting in sql/ looking like a safety net.

View on GitHub →