Changelog

v1.1.0

Clones match their source's SpinupWP settings, plus `spinuptui siblings` · September 30, 2026

A cloned site now matches its source's SpinupWP settings, not just its files and database, and the deploy script puts itself back. SpinupWP's new site-settings API made both possible. There's also a new CLI command for problems that belong to the whole server rather than one site: spinuptui siblings lists everyone else on the box.

Highlights

  • Clones match the source's SpinupWP settings. Creating a site through SpinupWP's API only sets page caching on or off, so a clone used to get SpinupWP's defaults for everything else. The wizard now copies:

    • page cache duration and exclusion lists,
    • the security toggles (PHP in uploads, xmlrpc.php, multisite subdirectory rewrites),
    • path redirects,
    • the WP cron interval, read from the site's crontab since the API doesn't report it.

    Only what differs is written, so a retry changes nothing, and nothing the clone already has is removed. The verify pane (v) lists what it matched and anything that didn't take, and w opens the new site in SpinupWP to finish it.

  • The deploy script puts itself back. SpinupWP clears a deploy script set when a site is created. Now that its API can update a site's Git settings, the wizard sets the source's script again once the site is done, and fixes push-to-deploy the same way. The g copy-and-open fallback from 1.0 only appears if the script still doesn't stick.

  • Basic auth is flagged. SpinupWP never reveals a site's basic-auth password, so a password-protected source can't be copied. Verify says so, and w opens the new site to set it.

  • spinuptui siblings <domain> — who else is on this server. Prints every site sharing a server with the one you name, as JSON, with the server's IP, SSH port, size and Ubuntu version. For each site it shows whether it's the server's vanity host, WordPress or not, its PHP version, whether page cache is on, and whether SpinupTUI set up Uptime Kuma monitors for it. It's for symptoms that belong to the whole box: a vanity host's ?healthz trips on whatever load the busiest co-tenant is making, and site isolation means the vanity site's own user can't see any of it. --probe also SSHes into each site user to show whose logs this device can actually read. A site that comes back permission_denied is one key grant (K) away.

Fixed

  • spinuptui ssh reports a hung connection as connection_failed, instead of an unexplained ssh_error, when its connectivity probe runs past 15 seconds.

Notes

  • Backups don't carry over to a clone yet. SpinupWP stores backups per domain, so a clone backing up before DNS moves would write into the production site's folder. Switch backups on for the new site after cutover; having the wizard do it at the cutover step is planned.

View on GitHub →