The clone wizard grew up on a real production migration. Every failure from a six-round, five-site server move was diagnosed from the wizard's own logs and fixed — plus the features that fell out of the fight.
Highlights
- Clones follow reality, not settings. The pull now detects where WordPress actually lives (
public_folderis a setting — SpinupWP never moves files for you) and normalizes mid-move layouts on the destination, keepingwp-config.phpone level above apublic/-style webroot per the config-outside-the-docroot convention. - Files-only clones. Non-WordPress sites (redirect shells, static/PHP) are now cloneable — opt-in in Plan, created with no database, verified by file count, size, and HTTP.
- Additional domains carry over with their redirect settings, so a cloned site answers for every hostname the source did — before,
www.and friends would have pointed at a server that didn't serve them. - Live transfer progress. The roster shows bytes, rate, and elapsed per stage — with a soft ceiling for file pulls and a true percent for database pulls.
- Every clone writes a full log (
~/.config/spinupwp-tui/logs/, passwords redacted, self-pruning at 30 days / 20 jobs).⏎on a failed site shows the complete error;rretries just that site. - The cutover waits for you. No more auto-advancing to the live-traffic step: review the settled roster, then
cto continue. On the cutover screen,↑↓/spaceinclude or exclude records, and⏎opens a manual record's registrar console with the zone name copied — hand-managed registrars show your DNS access note instead of a "connect an account" scold. - Dev Mode (
SPINUP_DEV_MODE=1). A fully interactive fake fleet — no token, no network, nothing that can touch a real account. Demos, screenshots, and UI work with a purpleDEV MODEbadge so it's unmistakable.
Fixed
- Concurrent clones no longer sabotage each other's SSH (the pull key is now per site — previously at most one site per run could survive).
- A file changing on the live source mid-transfer no longer kills the clone (tar's warning exit is tolerated and the culprit file is logged).
- Large transfers get a 60-minute budget instead of being killed at 15 by the wizard's own stacked timeouts — and a real timeout says so plainly.
- The API client paces itself off
X-RateLimit-Remainingand absorbs 429s with Retry-After; event polling tolerates transient read errors (rate-limited reads were making successful operations report as failures). - Cloned databases keep the source's table prefix instead of always
wp_.