Changelog

What's new in SpinupTUI

Page 4 of 6.

v0.18.0

Site status column + plugins/themes over SSH

July 7, 2026

Two additions to the Servers view, plus a stack-detection fix.

Highlights

  • At-a-glance status column. Every site row now shows a fixed-width capability strip β€” πŸ‘€πŸ”‘ granted SSH keys, H HTTPS, C page cache, B backups (lit when on, faint Β· when off), plus β—† linked and ↑N pending updates β€” aligned into columns across the whole list, with a compact key in the Sites panel title.
  • Installed plugins & themes (p). Press p on a site for its real wp plugin list / wp theme list over SSH: every plugin and theme with its status, current version, and available update (β†’ 1.2.3) β€” the detail the API only gives you as bare counts. Read-only; detects the WordPress directory itself, so it works on /public/ and Bedrock installs alike.

Fixed

  • Stack & type follow the d-identify probe, not SpinupWP's flag. is_wordpress is unreliable β€” false for Bedrock/git sites and for Standard-WP /public/ installs SpinupWP imported as "Generic" β€” so a real WordPress site could show as app (and its Details "Type" as Generic) even after d detected it. The row tag and Details fields now reflect the detected stack, and the plugins/themes view no longer refuses a misclassified WordPress site.

View on GitHub β†’

v0.17.0

per-site deploy keys for Bedrock clones

July 6, 2026

The clone wizard's Git-access step no longer shares one server key across every Bedrock repo β€” each site now brings its own read-only deploy key, generated on your machine and installed by SpinupWP as the new site's git identity.

Highlights

  • A unique deploy key per site. GitHub attaches a deploy key to exactly one repository account-wide, so the old server-key approach stopped working at the second Bedrock repo cloned to a server ("key is already in use"). The Git-access step now generates a fresh keypair per repo, puts the public half on the repo (auto via gh, with the title spinup-<domain>@<server>), and sends the pair with the site create β€” clone as many Bedrock repos to one server as you like.
  • Manual path included. No gh, or a repo off GitHub? The step shows each repo's generated key: o opens the repo's deploy-key settings page, and the new y copies the key to your clipboard.
  • Private keys stay private. The pair lives in memory for the length of the wizard, is never written to config, and is registered with the clone log's redaction.

Notes

  • Proven live end to end against a temporarily private repo where only the fresh per-site key could grant access β€” SpinupWP used it for the create-time clone and the full Bedrock clone passed.
  • Keys already added by older versions keep working; they're simply no longer reused for new sites.

πŸ€– Generated with Claude Code

View on GitHub β†’

v0.16.1

alert toggle covers every monitor

July 5, 2026

A patch release for the alert wiring shipped in v0.16.0: toggling a notification provider from the site-monitoring overlay now reaches every monitor Spinup registered for the site β€” including the Redis sentinel.

Fixed

  • Alert wiring (n) covers all of a site's monitors. The toggle worked from a hardcoded monitor list that predated the Redis sentinel, so ⏎ silently skipped the {server} redis check β€” "now alerts for 2 monitors" on a server that has 3. Monitors are now collected by convention from the saved refs, so the Redis sentinel β€” and any monitor kind added in the future β€” is wired automatically. If you toggled a provider on before this fix, open n again: it shows ◐ some monitors only, and one ⏎ attaches it to the rest.
  • The server-create wizard's monitor step no longer drops previously saved Redis/front-page monitor references when re-run.

πŸ€– Generated with Claude Code

View on GitHub β†’

v0.16.0

Site monitoring: fingerprints, a doctor, and a Redis sentinel

July 4, 2026

We've engineered a monitoring solution that's state-of-the-art for SpinupWP fleets β€” per dollar and per gram of installed weight. Zero agents, zero SaaS, nothing installed on your sites: every check runs from Uptime Kuma and a one-line cron you already had. The parts are commodity; the composition is the invention β€” each check deliberately watches either through the page cache (is the right thing being served?) or around it (is the machinery behind it alive?).

Highlights

  • The front-page check (f). The page cache can serve the wrong page while HTTP stays 200 β€” two production incidents showed a search-results template where the home page belonged, and every up/down monitor stayed green. Instead of a hand-picked headline keyword (which breaks the day someone edits the copy), Spinup reads your healthy front page, derives a template-identity fingerprint from what WordPress itself stamps into the markup (class="home, page-id-N, …), proves it discriminates against a throwaway search render, and registers the Kuma keyword monitor for you β€” at your chosen window (5m–1h; the check is served straight from the page cache, so it costs the site nothing). Red shows as WRONG PAGE SERVED in Details. Re-running f recalibrates the same monitor in place β€” history survives a redesign.
  • The site doctor (d). Read-only, zero setup, works without Kuma. It fetches your page twice β€” once normally, once with the cache-bypass cookie β€” and lets the server's own fastcgi-cache: HIT/BYPASS headers prove which layer answered each request, then compares template identity between the two: "the cache is lying" becomes a demonstrated fact with a copyable runbook, not a hunch. It also knocks on the wp-admin door (the login page β€” never cached; Bedrock's relocated /wp/ login handled; protected logins report "can't judge", never a false alarm).
  • The partial-outage verdict. The nastiest failure shape we found β€” verified live: with SpinupWP's default object-cache drop-in, a dead Redis is fatal (HTTP 500) for every request that misses the page cache. Cached pages keep serving 200, so visitors look fine while wp-admin, logged-in users and everything dynamic is broken β€” and page-watching monitors sleep through all of it. The doctor now diagnoses it explicitly (a PHP fatal in a plugin/theme produces the same signature and is caught the same way, including admin-only fatals via the door probe).
  • The Redis sentinel. One per server, riding the existing heartbeat cron: redis-cli ping every minute, pushed to its own {server} redis monitor that alerts independently. Registered by a/R on a vanity site β€” after probing that Redis actually answers on that box β€” and its token rotates with r like every other secret. Given the fatal-on-cache-miss behavior above, this one-minute sentinel is the primary detector for a real partial outage.
  • Alert wiring (n). Spinup detects the notification providers configured in your Kuma β€” by name, not assumed β€” and shows whether each is attached to this site's monitors (βœ“ all / ◐ some / β—‹ none); ⏎ toggles a provider across all of the site's checks at once, editing monitors in place. Creating the provider (bot tokens etc.) stays in Kuma; wiring it to sites now lives in Spinup.
  • M everywhere. The site-monitoring overlay opens with capital M from Servers, Stacks and Search alike (Servers keeps lowercase m too) β€” one muscle-memory key across the app.

Fixed

  • A finished operation's message no longer hides the monitoring overlay's action menu for the rest of the session β€” results show above the menu, and the overlay always reopens fresh.
  • The ?/i help overlays could deadlock open if triggered in the beat before a view's text input grabbed focus; dismissal now runs first.

Notes

  • Every claim above was verified against live infrastructure before shipping: body-class fingerprints on the incident-prone production sites, fastcgi-cache headers on two servers, the drop-in's exception handling read from source, and a full stop-Redis/watch-it-alert/restart cycle on the test box.
  • Honest boundary: this is not APM-grade observability β€” it's the meaningful subset for this stack, at effectively zero cost and zero installed weight. Checks that can't prove something say "can't judge" instead of guessing.
  • A per-site health endpoint (deeper internals: eviction thrash, graceful-mode inventory, DB health) is designed and deliberately parked for a future release.

πŸ€– Generated with Claude Code

View on GitHub β†’

v0.15.0

rotate monitoring secrets in place

July 4, 2026

Record your screencast with the push URL on screen, then press one key and it's dead: r rotates a vanity site's monitoring secrets in place β€” no monitor deleted, no history lost. Plus vanity sites now stand out in the Servers tab.

Highlights

  • Rotate monitoring secrets (r in the m overlay). Two secrets can end up on screen in a recording: the Kuma push URL (Kuma displays it in full) and the health key in a ?format=json&key=… URL. r on a vanity site mints fresh ones and kills the old ones immediately β€” a new push token is edited into the existing push monitor (same monitor row: heartbeat history, uptime stats and notification wiring all survive), the heartbeat cron is rewritten over SSH, a new health key is re-seeded into the page, and any Kuma monitor URL still embedding the old key is re-keyed automatically. Confirm-gated; expect at most a missed beat or two, absorbed by the monitor's retries.
  • Works without Kuma too. Unconnected, r still rotates the health key (there's no push monitor to edit) and says so.
  • Vanity sites stand out in the Servers tab. The server's own vanity/health page is marked βŒ‚ with a brand-green tint in the sites list β€” with servers named like domains (the vanity convention), it otherwise hides among regular sites.

Notes

  • Rotation never deletes or re-creates monitors β€” it uses Kuma's edit API, so dashboards, status pages and notification assignments keep pointing at the same monitor.
  • The old push URL stops accepting beats the moment the rotation lands; the old health key starts returning 403 as soon as the page is re-seeded.
  • Acceptance-tested against a live Uptime Kuma instance and a real server: history intact across rotation, old secrets verified dead, new heartbeat flowing within a minute.

πŸ€– Generated with Claude Code

View on GitHub β†’

v0.14.0

Uptime Kuma integration

July 4, 2026

Spinup meets your monitoring: vanity pages become health endpoints any uptime tool can watch, and with an Uptime Kuma connection the monitors set themselves up β€” load graphs, dead-man's-switch heartbeats, sparklines in the Health view, and maintenance windows around reboots.

Highlights

  • Vanity pages double as health endpoints. The page the V wizard seeds now answers ?healthz β€” plain 200 ok, or 503 when 1-min load per core tops 2 or disk free drops under 10% β€” so any plain HTTP monitor gets resource alerting from the status code alone. ?format=json&key=… serves full metrics (load, cores, uptime, disk, memory, PHP version) behind a per-site key generated at seed time. Tool-agnostic by design; recipes in docs/uptime-kuma.md.
  • Site monitoring (m). Press m on a site to wire it into your own Uptime Kuma (one-time connect with a real login check; 2FA supported β€” the code is asked exactly once, then a stored token covers every later session). Vanity sites get the full treatment: a healthz monitor plus a load push monitor fed by a once-a-minute cron β€” Kuma graphs server load, and a silent cron (server down, cron dead, egress broken) flips the monitor. Regular sites get a homepage monitor with cert-expiry alerts; client site files are never touched. R refreshes an existing vanity page to the current version β€” with or without Kuma.
  • The V wizard registers monitors automatically. With Kuma connected, two new steps after publishing the page: register both monitors, install the heartbeat cron. They auto-skip when Kuma isn't set up, and a monitoring failure is skippable β€” the site is already live.
  • Kuma status flows back into Spinup. A Monitor row per site in Details, a β–Ό N monitors down header badge (silent when all's well), and a Monitor panel in the Health view (h) with 24h uptime, response-time and server-load sparklines β€” real history that survives reopening the view.
  • Reboots never page you. Firing a reboot first wraps the server's monitors in a Kuma maintenance window and removes it when the reboot settles. Strictly best-effort: Kuma being unreachable never blocks the reboot.

Notes

  • Monitors are adopted, not duplicated: same-named monitors in Kuma are reused, a hand-made push monitor keeps its token, and recorded ids are re-verified against Kuma before being trusted (deleting a monitor there and pressing a re-creates it).
  • Load pushes are sent Γ—100 as integers (some Kuma builds silently drop float pings); Spinup's views scale them back.
  • Connection lives in config.json (0600) or via SPINUP_KUMA_URL / _USERNAME / _PASSWORD. Speaks Kuma's socket.io API; handles both 1.x and 2.x monitor schemas. Dev Mode never touches a real Kuma.
  • New dependency: socket.io-client β€” run bun install after updating.

View on GitHub β†’

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 β†’

v0.12.0

A "Battle-Tested" Clone Wizard

July 3, 2026

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_folder is a setting β€” SpinupWP never moves files for you) and normalizes mid-move layouts on the destination, keeping wp-config.php one level above a public/-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; r retries just that site.
  • The cutover waits for you. No more auto-advancing to the live-traffic step: review the settled roster, then c to continue. On the cutover screen, ↑↓/space include 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 purple DEV MODE badge 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-Remaining and 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_.

View on GitHub β†’

v0.11.0

Release notes, in-app updates, HTTPS toggle, cache purge

July 2, 2026

Four new capabilities, all tracked in the background the same way every write in Spinup already is.

Highlights

  • "What's new" release notes. After Spinup updates, a one-time overlay shows what changed β€” sourced straight from GitHub, no separate feed to maintain. Press n in ? Help any time to replay the current version's notes.
  • Update in place with u. The gold ✦ vX.Y.Z hint now has a matching action: u in ? Help runs git pull --ff-only right there β€” refuses on a dirty checkout or diverged history, and always tells you to restart afterward (with a bun install nudge if dependencies changed).
  • Enable / disable HTTPS (H). Direction auto-derived from the site's current state; disabling explicitly warns that https:// visitors will see errors until it's re-enabled.
  • Purge page + object cache (P). SpinupWP has no enable/disable for either cache on an existing site β€” only purge β€” so P fires both together under one confirm.

Fixed

  • Cloudflare proxied DNS records no longer get excluded from the clone wizard's DNS cutover β€” their origin IP was always safely repointable even though their TTL stays fixed to automatic.
  • The release-notes overlay no longer overlaps text on long, word-wrapped bullets.

View on GitHub β†’

v0.10.0

Fleet-wide EOL signals + DNS access notes

July 1, 2026

Two new fleet-visibility signals: know which servers need an OS upgrade, and never lose track of who actually has access to a client's DNS.

Highlights

  • Servers running an end-of-life Ubuntu release are flagged. A ⚠ os badge in the Servers list, a red "Ubuntu … EOL" line in the server detail panel, and a "Needs attention" entry on the Dashboard pointing straight at the clone wizard (C). EOL dates come from the same embedded-plus-live-refresh approach already used for PHP EOL, so it stays current without a release.
  • Access notes for zones you can't reach via API. Any β†— web-only host (GoDaddy, Namecheap, Network Solutions, …) now shows an assumed default ("Delegate Access") or your own per-zone override in the DNS inventory's NOTE column. Press c "Manage Access" on any such zone to see every zone already known at that host, n to edit a note, or r to resolve your whole fleet's DNS and fill in any gaps.

Notes

  • Only note exceptions are ever stored β€” the common case (you manage a registrar the same way everywhere) costs zero config.
  • Both signals are entirely read-only β€” no writes, no confirm overlay needed.

View on GitHub β†’