Changelog

v1.0.0

Homebrew install, Radicle clones, and your cron jobs come along · September 24, 2026

SpinupTUI reaches 1.0. It installs with one Homebrew command, the clone wizard now handles Radicle sites and brings your cron jobs along, and the header shows how much of your API budget is left before you run into it. From here on, SemVer applies properly: breaking changes to commands, flags or the config file mean a major version.

Highlights

  • Install with Homebrew. brew install mwender/tap/spinuptui installs SpinupTUI and Bun together, and brew upgrade spinuptui keeps it current. The About panel (?) recognizes a Homebrew install and shows that command. Installs use the exact dependency versions this release was tested with.
  • Clone Radicle sites. Git-deployed Radicle sites now clone properly:
    • Uploads come across from content/uploads.
    • After the database import, the site's own deploy script runs on the new server, so the front-end is built (npm ci, npm run build, Acorn caches) just as a normal deploy would build it.
    • Before creating anything, the wizard stops if the site has no deploy script, or if its script needs Node and the destination doesn't have it. SpinupWP servers don't come with Node, so install it on the destination first.
  • Clones keep your cron jobs. Lines you added to a site's crontab (a feed import, a report, an Acorn or Laravel command) are copied to the clone under a # Carried over from … comment. Commented-out lines stay commented, SpinupWP's own WordPress cron entry is left to SpinupWP, and a retry never adds a line twice.
  • Clones match the source's settings. Page cache, push-to-deploy and the deploy script now come from the source site instead of fixed defaults.
  • API headroom in the header. API 52/60 shows how many SpinupWP API requests are left this minute. It's dim while there's plenty, amber once three-quarters are spent, and red when SpinupTUI starts spacing out requests, so a slow moment has a visible reason.

Fixed

  • Plugins & themes (e) no longer shows an empty list on sites with noisy plugins. Some plugins print PHP notices into wp-cli's output, sometimes on the same line as the plugin list. The list is now found wherever it sits, and if wp-cli returns no list at all, the view says so and shows what it printed instead. The WordPress core update check uses the same parsing.

Notes

  • SpinupWP clears a deploy script set through its API a minute or two after a site is created, and there's no API call to set it afterwards. After a clone, the wizard checks the new site. If the script is gone, the roster marks the site, and in the verify pane (v) g copies the source's script and opens the new site's Git settings so you can paste it back. The same check flags a push-to-deploy setting that didn't carry over.

View on GitHub →