<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>SpinupTUI</title>
  <subtitle>News and releases</subtitle>
  <link href="https://spinuptui.com/feed.xml" rel="self"/>
  <link href="https://spinuptui.com/"/>
  <id>https://spinuptui.com/</id>
  <updated>2026-11-10T16:25:41.000Z</updated>
  <author><name>SpinupTUI</name></author>
  <entry>
    <title>SpinupTUI v1.3.0: Modules: Beacon, Scheduler and Sentinel</title>
    <link href="https://spinuptui.com/changelog/v1.3.0/"/>
    <id>https://spinuptui.com/changelog/v1.3.0/</id>
    <updated>2026-11-10T16:25:41.000Z</updated>
    <content type="html">&lt;p&gt;&lt;strong&gt;SpinupTUI now keeps working after you close it.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Modules are parts of SpinupTUI that run on their own, on a Mac that stays awake. We call that Mac a &lt;em&gt;station&lt;/em&gt;. Three ship today, and each builds on the one before:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Sentinel&lt;/strong&gt; watches your fleet and works out what broke.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Beacon&lt;/strong&gt; pages you.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Scheduler&lt;/strong&gt; runs follow-ups on a clock.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Set them up from the new &lt;strong&gt;Modules&lt;/strong&gt; tab (&lt;code&gt;6&lt;/code&gt;). It shows what each step will change before it changes anything.&lt;/p&gt;
&lt;p&gt;📣 &lt;strong&gt;The story behind this release:&lt;/strong&gt; &lt;a href="https://spinuptui.com/news/spinuptui-1-3-0-modules/"&gt;SpinupTUI 1.3.0: modules that keep watch after you close it&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;◈ Sentinel: know &lt;em&gt;why&lt;/em&gt;, not just that it's down&lt;/h2&gt;
&lt;p&gt;Every 5 minutes, Sentinel checks Uptime Kuma and groups whatever went down by server. Then it pages you and writes it up.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bring an agent CLI&lt;/strong&gt; (Claude Code or Codex) for a full diagnosis. Without one, you still get the evidence.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The agent can only read.&lt;/strong&gt; It reaches servers through &lt;code&gt;ssh-exec&lt;/code&gt;, and it can't post anything.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sentinel files the report&lt;/strong&gt; on your team's Basecamp board and pages you a one-line summary that names the site to blame.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A repeat within 6 hours&lt;/strong&gt; becomes a follow-up on the same report, not a new one.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;And a morning digest that only speaks up about what's new.&lt;/strong&gt; At 08:00 it covers station health, the last 24 hours, server updates, and things monitoring can't see, like a crawler that stopped arriving. When nothing needs you, it stays quiet.&lt;/p&gt;
&lt;h2&gt;◉ Beacon: one command that pages you&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;spinuptui beacon send&lt;/code&gt;&lt;/strong&gt; works from any script, cron job or agent. It pages you on Telegram, with retries and a send log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Guided setup&lt;/strong&gt; makes the Telegram bot with you.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Your pager answers back.&lt;/strong&gt; Send &lt;code&gt;/jobs&lt;/code&gt; to see the station's jobs, extend one that's about to expire, or run a failed one again.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;◷ Scheduler: follow-ups that run themselves&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Queue &amp;quot;check this tomorrow at 8&amp;quot;&lt;/strong&gt; from any session, and the result arrives through Beacon.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A job can be&lt;/strong&gt; a SpinupTUI command, a script, or a read-only agent prompt.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every job expires&lt;/strong&gt;, so a forgotten one stops by itself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Station heartbeat:&lt;/strong&gt; each tick pings an Uptime Kuma monitor you run elsewhere, so you notice when the station itself stops.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Also new&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Choose how often Kuma checks a site:&lt;/strong&gt; 1, 2, 5 or 10 minutes, from the monitoring overlay (&lt;code&gt;M&lt;/code&gt;). Thanks to &lt;a href="https://github.com/lumpysimon"&gt;@lumpysimon&lt;/a&gt; for the request.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Headless commands start about 3× faster.&lt;/strong&gt; That matters for something started every five minutes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A reboot's Kuma maintenance window now ends by itself after 30 minutes.&lt;/strong&gt; Before, quitting mid-reboot could leave monitors in Maintenance, where they never alert.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Stations are macOS-only for now.&lt;/strong&gt; The rest of SpinupTUI is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Basecamp reports post as whoever the Basecamp CLI is logged in as.&lt;/strong&gt; We recommend a separate Basecamp user. &lt;a href="https://github.com/mwender/spinupwp-tui/blob/v1.3.0/docs/sentinel.md#who-reports-post-as"&gt;How to set that up&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;On a 1.3.0 alpha?&lt;/strong&gt; There's nothing to migrate. Move from &lt;code&gt;@next&lt;/code&gt; to &lt;code&gt;@latest&lt;/code&gt;, or to Homebrew.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Docs:&lt;/strong&gt; &lt;a href="https://github.com/mwender/spinupwp-tui/blob/v1.3.0/docs/sentinel.md"&gt;Sentinel&lt;/a&gt; · &lt;a href="https://github.com/mwender/spinupwp-tui/blob/v1.3.0/docs/scheduler.md"&gt;Scheduler&lt;/a&gt; · &lt;a href="https://github.com/mwender/spinupwp-tui/blob/v1.3.0/docs/beacon.md"&gt;Beacon&lt;/a&gt; · &lt;a href="https://spinuptui.com"&gt;spinuptui.com&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI 1.3.0: modules that keep watch after you close it</title>
    <link href="https://spinuptui.com/news/spinuptui-1-3-0-modules/"/>
    <id>https://spinuptui.com/news/spinuptui-1-3-0-modules/</id>
    <updated>2026-11-10T12:00:00Z</updated>
    <content type="html">&lt;p&gt;Until now, SpinupTUI only worked while it was open. That's fine for checking on a fleet, but outages don't wait for you to open a terminal.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SpinupTUI 1.3.0 adds modules: parts of the app that keep working after you quit.&lt;/strong&gt; Put SpinupTUI on a Mac that stays awake, turn the modules on, and walk away. We call that Mac a &lt;em&gt;station&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Three modules ship today.&lt;/p&gt;
&lt;h2&gt;◈ Sentinel works out what broke&lt;/h2&gt;
&lt;p&gt;Uptime monitoring tells you a site is down. It doesn't tell you why, and the why is where the time goes.&lt;/p&gt;
&lt;p&gt;Sentinel checks Uptime Kuma every five minutes. When something goes down, it:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Groups it by server&lt;/strong&gt;, so five monitors paging for one overloaded box is one incident, not five.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pages you right away&lt;/strong&gt; with what it knows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gathers the evidence&lt;/strong&gt;: the server's load and memory, the other sites on the box, and whether the page is really failing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Diagnoses it&lt;/strong&gt;, if you bring an agent CLI like Claude Code or Codex. The agent can only &lt;em&gt;read&lt;/em&gt; your servers, and it can't post anything.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Files the report&lt;/strong&gt; on your team's Basecamp board, then pages you a one-line summary that names the site to blame.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The site that pages often isn't the site that caused it. Sentinel looks at the whole box before it decides.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Every morning at 8:00, you get a digest&lt;/strong&gt;, and it only speaks up about what's new. It covers the last 24 hours, pending server updates, and things uptime monitoring can't see, like a crawler that stopped arriving or a cache that stopped hitting.&lt;/p&gt;
&lt;h2&gt;◉ Beacon pages you&lt;/h2&gt;
&lt;p&gt;Beacon is one command, &lt;code&gt;spinuptui beacon send&lt;/code&gt;, that pages you on Telegram. Sentinel uses it, and so can any script, cron job or agent of your own.&lt;/p&gt;
&lt;p&gt;Your pager can also answer back. Send &lt;code&gt;/jobs&lt;/code&gt; to see what the station is running, extend a job that's about to expire, or run a failed one again.&lt;/p&gt;
&lt;h2&gt;◷ Scheduler follows up&lt;/h2&gt;
&lt;p&gt;You fixed something today. Will you remember to check it tomorrow?&lt;/p&gt;
&lt;p&gt;Scheduler remembers for you. Queue &amp;quot;check this tomorrow at 8&amp;quot; from any session, and the station runs it and sends you the result. A job can be a SpinupTUI command, a script, or a read-only agent prompt. Every job has an expiry date, so a forgotten one stops by itself.&lt;/p&gt;
&lt;h2&gt;Its first week on a real fleet&lt;/h2&gt;
&lt;p&gt;Before calling it stable, we ran Sentinel on our own production fleet for a week.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;2,010 of 2,010 checks ran&lt;/strong&gt;, one every five minutes, with no failures.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;18 incidents&lt;/strong&gt;, every one diagnosed, written up and posted to the board.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Real finds:&lt;/strong&gt; a database server killed for memory during an unattended upgrade, a plugin fatal on PHP 8 that a bot kept setting off, and scanners knocking over sites with request bursts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One bug,&lt;/strong&gt; in how Sentinel read an &amp;quot;already documented&amp;quot; answer. It's fixed in this release.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Also in 1.3.0&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Choose how often Uptime Kuma checks a site:&lt;/strong&gt; every 1, 2, 5 or 10 minutes. Thanks to &lt;a href="https://github.com/lumpysimon"&gt;@lumpysimon&lt;/a&gt; for the request.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Headless commands start about three times faster.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A reboot's Kuma maintenance window now ends by itself&lt;/strong&gt; after 30 minutes, so monitors never stay silenced.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Get it&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt;brew install mwender/tap/spinuptui
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Already on SpinupTUI? Run &lt;code&gt;brew upgrade spinuptui&lt;/code&gt;, or &lt;code&gt;bun add -g spinuptui@latest --no-cache&lt;/code&gt;. Then open the &lt;strong&gt;Modules&lt;/strong&gt; tab (&lt;code&gt;6&lt;/code&gt;). Each module shows what it will change before it changes anything.&lt;/p&gt;
&lt;p&gt;Stations are macOS-only for now. Everything else in SpinupTUI works as before.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.2.2: Kuma behind proxies, www-canonical pulls, mixed-stack media</title>
    <link href="https://spinuptui.com/changelog/v1.2.2/"/>
    <id>https://spinuptui.com/changelog/v1.2.2/</id>
    <updated>2026-11-06T17:27:25.000Z</updated>
    <content type="html">&lt;p&gt;A small fix release: three bugs, all found on real sites. Uptime Kuma connects through proxies that block WebSockets, &lt;code&gt;pull db&lt;/code&gt; stops leaving production URLs behind, and the media fallback works while a site is mid-conversion to Bedrock.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Uptime Kuma connects through proxies that block WebSockets.&lt;/strong&gt; SpinupTUI was meant to fall back to plain HTTP when a WebSocket failed, but the fallback never actually ran. So a reverse proxy or CDN that doesn't pass WebSocket upgrades failed the whole connection, though Kuma also answers over HTTP. It now retries over HTTP. If both attempts fail, the error gives each one's real reason (e.g. &lt;code&gt;Expected 101 status code (WebSocket); HTTP 404 (polling)&lt;/code&gt;), where before it said only &lt;code&gt;websocket error&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;pull db&lt;/code&gt; rewrites a &lt;code&gt;www.&lt;/code&gt; site's URLs.&lt;/strong&gt; The rewrite started from the SpinupWP domain. So a site whose domain is &lt;code&gt;example.com&lt;/code&gt; but whose WordPress home is &lt;code&gt;https://www.example.com&lt;/code&gt; kept every &lt;code&gt;www.&lt;/code&gt; URL pointing at production, even though every step showed ✓. The pull now asks production for its home URL over the same SSH connection as the export, and rewrites that as well as the domain. Post-import hooks get the home URL's host as &lt;code&gt;SYNC_REMOTE_HOST&lt;/code&gt;, and every rewritten host in the new &lt;code&gt;SYNC_REMOTE_HOSTS&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;pull db&lt;/code&gt; rewrites URLs in plugin tables too.&lt;/strong&gt; wp-cli's &lt;code&gt;search-replace&lt;/code&gt; covers only WordPress's core tables unless told otherwise. So Yoast's indexables (and with them the local copy's canonical and schema URLs), cache and log tables, and form entries all kept production URLs. The rewrite now covers every table with the site's prefix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The production media fallback (&lt;code&gt;m&lt;/code&gt;) works when production runs a different stack.&lt;/strong&gt; When a Standard WP site had been converted to Bedrock locally but production hadn't been switched yet, every missing image pointed at production's &lt;code&gt;/app/uploads&lt;/code&gt;, which doesn't exist there, while the dialog said ON. The plugin (now v3) maps the local uploads path to production's, based on production's stack. The &lt;code&gt;m&lt;/code&gt; dialog shows the mapping when the two differ. Press &lt;code&gt;u&lt;/code&gt; in the &lt;code&gt;m&lt;/code&gt; dialog to update an installed plugin.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.2.1: Fresh WordPress versions, and w opens the right page</title>
    <link href="https://spinuptui.com/changelog/v1.2.1/"/>
    <id>https://spinuptui.com/changelog/v1.2.1/</id>
    <updated>2026-10-27T14:07:14.000Z</updated>
    <content type="html">&lt;p&gt;A small fix release. WordPress versions stay current without you doing anything, and &lt;code&gt;w&lt;/code&gt; opens the site or server you picked in SpinupWP instead of the dashboard.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;WordPress versions no longer go stale.&lt;/strong&gt; SpinupTUI read a site's WordPress version once, when it first identified the site, and never again, so sites updated outside SpinupTUI (auto-updates, wp-admin, deploys) kept showing an old version, and &lt;code&gt;r&lt;/code&gt; didn't help. Versions older than a day are now re-checked in the background whenever the site list loads. Each server's sites are checked one at a time, and the first failure on a server stops it for the day, so unattended SSH can't trip fail2ban. A reading that couldn't be refreshed shows its age in the Stacks list (&lt;code&gt;WordPress 6.9.4 4mo&lt;/code&gt;), and the Details pane always says when it was taken.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;w&lt;/code&gt; opens the right page.&lt;/strong&gt; Links into SpinupWP need your account slug, which SpinupWP's API doesn't provide and setup never asked for, so unless you'd added &lt;code&gt;accountSlug&lt;/code&gt; to your config by hand, &lt;code&gt;w&lt;/code&gt; fell back to the dashboard. Now &lt;code&gt;w&lt;/code&gt; asks for the slug the first time it needs it (pasting any dashboard URL works), saves it and opens the page you asked for. First-run setup also asks for it, as an optional step.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.2.0: Take sites offline until you can patch</title>
    <link href="https://spinuptui.com/changelog/v1.2.0/"/>
    <id>https://spinuptui.com/changelog/v1.2.0/</id>
    <updated>2026-10-21T13:12:24.000Z</updated>
    <content type="html">&lt;p&gt;When a server can't be patched yet against a critical vulnerability, the advice is to take its sites offline until it can be. SpinupTUI now does that a whole server at a time, or one site at a time, and remembers exactly what it took down, so bringing everything back is one step and never touches a site you'd disabled for some other reason.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Take a server's sites offline (&lt;code&gt;a&lt;/code&gt;).&lt;/strong&gt; The server actions menu has a new last row, &lt;strong&gt;Take all N sites offline&lt;/strong&gt;. It uses SpinupWP's own disable setting: nginx stops answering for every domain on those sites, so visitors can't connect and no request reaches PHP, including requests aimed straight at the server's IP. Files, databases and certificates are untouched. On a server SpinupTUI took offline, the same row becomes &lt;strong&gt;Bring N sites back online&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Or one site (&lt;code&gt;O&lt;/code&gt;).&lt;/strong&gt; Press &lt;code&gt;O&lt;/code&gt; on a site in Servers, Search or Stacks, and &lt;code&gt;O&lt;/code&gt; again to bring it back. PHP is shared by every site on a server, so the confirmation tells you how many other sites are still up and points you to &lt;code&gt;a&lt;/code&gt; when it's the server you need to protect.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It brings back exactly what it took down.&lt;/strong&gt; Each site is recorded the moment SpinupWP accepts its disable, so an interrupted run can still be undone. A site disabled some other way stays disabled, a failed re-enable stays recorded so running it again finishes the job, and sites taken offline one at a time come back with their server.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;From the command line too.&lt;/strong&gt; &lt;code&gt;spinuptui offline &amp;lt;server&amp;gt;… --yes&lt;/code&gt; and &lt;code&gt;spinuptui online &amp;lt;server&amp;gt;… --yes&lt;/code&gt;, plus &lt;code&gt;--all&lt;/code&gt; for every server and &lt;code&gt;--site &amp;lt;domain&amp;gt;&lt;/code&gt; for one site. Without &lt;code&gt;--yes&lt;/code&gt; they print the plan and change nothing. &lt;code&gt;spinuptui offline&lt;/code&gt; on its own lists what's offline. Servers must be named exactly (name, IP or id); a partial name is refused with suggestions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No alert flood.&lt;/strong&gt; With Uptime Kuma connected, the affected sites' monitors go into one maintenance window per server. Sites leave it as they come back, and the window is removed when the last one does.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You can see what's down.&lt;/strong&gt; Offline sites show &lt;code&gt;⏻ off&lt;/code&gt; in the site list. Servers show &lt;code&gt;⏻ off&lt;/code&gt; when all their sites are offline and &lt;code&gt;⏻ 3 off&lt;/code&gt; when some are, and they're listed under the Overview's &amp;quot;Needs attention&amp;quot;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Offline means a connection error, not a maintenance page.&lt;/strong&gt; Visitors see their browser's &amp;quot;can't connect&amp;quot; message. Disabling or re-enabling a site takes a few seconds; SpinupWP works through one server's sites in turn, so a server with 20 sites takes a minute or two.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The site's PHP-FPM pool and cron keep running.&lt;/strong&gt; The pool only listens on a local socket, so it isn't reachable from outside.&lt;/li&gt;
&lt;li&gt;Details in &lt;a href="https://github.com/mwender/spinupwp-tui/blob/v1.2.0/docs/taking-sites-offline.md"&gt;docs/taking-sites-offline.md&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.1.2: ssh-exec allows quoted wp flags; Kuma errors show their cause</title>
    <link href="https://spinuptui.com/changelog/v1.1.2/"/>
    <id>https://spinuptui.com/changelog/v1.1.2/</id>
    <updated>2026-10-15T20:19:28.000Z</updated>
    <content type="html">&lt;p&gt;A small fix release. &lt;code&gt;spinuptui ssh-exec&lt;/code&gt; stops refusing a harmless WP-CLI read, and a failed Uptime Kuma connection now tells you why it failed.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A quoted &lt;code&gt;wp&lt;/code&gt; command that ends in a flag is allowed.&lt;/strong&gt; &lt;code&gt;spinuptui ssh-exec &amp;lt;site&amp;gt; -- bash -c 'wp --info'&lt;/code&gt; was denied because the closing quote landed on the flag and the guard read it as an option missing its value.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Uptime Kuma connection errors show the actual reason.&lt;/strong&gt; With a long instance URL, the cause (a TLS, DNS or proxy problem, say) ran past the edge of the connect form, leaving only &lt;code&gt;Couldn't reach Uptime Kuma at https://…:&lt;/code&gt;. The error lines in the connect form and the Alerts panel now wrap. If you couldn't connect before, update and try again: the message should now say what went wrong.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.1.1: ssh-exec's read-only guard closes its Redis and WP-CLI gaps</title>
    <link href="https://spinuptui.com/changelog/v1.1.1/"/>
    <id>https://spinuptui.com/changelog/v1.1.1/</id>
    <updated>2026-10-01T15:40:01.000Z</updated>
    <content type="html">&lt;p&gt;A fix release for &lt;code&gt;spinuptui ssh-exec&lt;/code&gt;, the command that lets an agent run diagnostics on a server without being able to change it. Its read-only guard let Redis writes and many WP-CLI writes through. Both are closed, and the update command now reliably fetches the newest version.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Redis writes are denied.&lt;/strong&gt; The guard had no rules for Redis, so &lt;code&gt;redis-cli CONFIG SET …&lt;/code&gt;, &lt;code&gt;FLUSHALL&lt;/code&gt;, &lt;code&gt;FLUSHDB&lt;/code&gt;, &lt;code&gt;BGSAVE&lt;/code&gt; and plain &lt;code&gt;SET&lt;/code&gt;/&lt;code&gt;DEL&lt;/code&gt; ran as if they were diagnostics. &lt;code&gt;redis-cli&lt;/code&gt; is now allowed only with a known read: &lt;code&gt;ping&lt;/code&gt;, &lt;code&gt;info&lt;/code&gt;, &lt;code&gt;dbsize&lt;/code&gt;, &lt;code&gt;lastsave&lt;/code&gt;, &lt;code&gt;config get&lt;/code&gt;, &lt;code&gt;memory doctor|stats|usage&lt;/code&gt;, &lt;code&gt;latency latest|history&lt;/code&gt;, &lt;code&gt;slowlog get|len&lt;/code&gt;, &lt;code&gt;client list|info&lt;/code&gt; and a few key-inspection reads. Everything else is denied, including unrecognised options and a bare &lt;code&gt;redis-cli&lt;/code&gt; fed from stdin.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unlisted WP-CLI writes are denied.&lt;/strong&gt; The guard named a dozen WP-CLI writes and allowed every other command, so &lt;code&gt;wp transient delete&lt;/code&gt;, &lt;code&gt;wp search-replace&lt;/code&gt;, &lt;code&gt;wp eval&lt;/code&gt;, &lt;code&gt;wp plugin uninstall&lt;/code&gt; and &lt;code&gt;wp cron event run&lt;/code&gt; got through. &lt;code&gt;wp&lt;/code&gt; is now allowed only with a known read (&lt;code&gt;plugin list&lt;/code&gt;, &lt;code&gt;option get&lt;/code&gt;, &lt;code&gt;core version&lt;/code&gt;, &lt;code&gt;cache type&lt;/code&gt;, &lt;code&gt;cron event list&lt;/code&gt;, &lt;code&gt;db size&lt;/code&gt; and the like), and &lt;code&gt;--exec&lt;/code&gt;, &lt;code&gt;--require&lt;/code&gt;, &lt;code&gt;--ssh&lt;/code&gt; and &lt;code&gt;--http&lt;/code&gt; are refused on any command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Denials say what was refused.&lt;/strong&gt; The message names the verb or option, for example &lt;code&gt;redis-cli `config set` is not on the read-only allowlist&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The update command now actually updates.&lt;/strong&gt; The About panel (&lt;code&gt;?&lt;/code&gt;) suggests &lt;code&gt;bun add -g spinuptui@latest --no-cache&lt;/code&gt;. Without &lt;code&gt;--no-cache&lt;/code&gt;, Bun can resolve &lt;code&gt;@latest&lt;/code&gt; from a cached copy of the package listing and reinstall the version you already have.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Changed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;wp user list&lt;/code&gt;, &lt;code&gt;wp user get&lt;/code&gt; and &lt;code&gt;wp user list-caps&lt;/code&gt; are allowed.&lt;/strong&gt; The guard used to refuse everything under &lt;code&gt;wp user&lt;/code&gt;, reads included. Creating, deleting and changing users is still denied.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Two reads that used to pass are now denied:&lt;/strong&gt; &lt;code&gt;wp config get&lt;/code&gt; and &lt;code&gt;wp config list&lt;/code&gt;, because they print the database password into the audit log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A WP-CLI read that isn't on the list is denied too&lt;/strong&gt;, where it used to pass. If a diagnostic you rely on is refused, open an issue and it can be added.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The guard still isn't a sandbox.&lt;/strong&gt; Outside &lt;code&gt;redis-cli&lt;/code&gt; and &lt;code&gt;wp&lt;/code&gt; it matches known-destructive patterns, so it catches mistakes, not a determined write.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.1.0: Clones match their source's SpinupWP settings, plus `spinuptui siblings`</title>
    <link href="https://spinuptui.com/changelog/v1.1.0/"/>
    <id>https://spinuptui.com/changelog/v1.1.0/</id>
    <updated>2026-09-30T21:37:37.000Z</updated>
    <content type="html">&lt;p&gt;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: &lt;code&gt;spinuptui siblings&lt;/code&gt; lists everyone else on the box.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Clones match the source's SpinupWP settings.&lt;/strong&gt; 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:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;page cache duration and exclusion lists,&lt;/li&gt;
&lt;li&gt;the security toggles (PHP in uploads, &lt;code&gt;xmlrpc.php&lt;/code&gt;, multisite subdirectory rewrites),&lt;/li&gt;
&lt;li&gt;path redirects,&lt;/li&gt;
&lt;li&gt;the WP cron interval, read from the site's crontab since the API doesn't report it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Only what differs is written, so a retry changes nothing, and nothing the clone already has is removed. The verify pane (&lt;code&gt;v&lt;/code&gt;) lists what it matched and anything that didn't take, and &lt;code&gt;w&lt;/code&gt; opens the new site in SpinupWP to finish it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The deploy script puts itself back.&lt;/strong&gt; 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 &lt;code&gt;g&lt;/code&gt; copy-and-open fallback from 1.0 only appears if the script still doesn't stick.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Basic auth is flagged.&lt;/strong&gt; SpinupWP never reveals a site's basic-auth password, so a password-protected source can't be copied. Verify says so, and &lt;code&gt;w&lt;/code&gt; opens the new site to set it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;spinuptui siblings &amp;lt;domain&amp;gt;&lt;/code&gt; — who else is on this server.&lt;/strong&gt; 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 &lt;code&gt;?healthz&lt;/code&gt; 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. &lt;code&gt;--probe&lt;/code&gt; also SSHes into each site user to show whose logs this device can actually read. A site that comes back &lt;code&gt;permission_denied&lt;/code&gt; is one key grant (&lt;code&gt;K&lt;/code&gt;) away.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;spinuptui ssh&lt;/code&gt; reports a hung connection as &lt;code&gt;connection_failed&lt;/code&gt;&lt;/strong&gt;, instead of an unexplained &lt;code&gt;ssh_error&lt;/code&gt;, when its connectivity probe runs past 15 seconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Backups don't carry over to a clone yet.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v1.0.0: Homebrew install, Radicle clones, and your cron jobs come along</title>
    <link href="https://spinuptui.com/changelog/v1.0.0/"/>
    <id>https://spinuptui.com/changelog/v1.0.0/</id>
    <updated>2026-09-24T16:43:49.000Z</updated>
    <content type="html">&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Install with Homebrew.&lt;/strong&gt; &lt;code&gt;brew install mwender/tap/spinuptui&lt;/code&gt; installs SpinupTUI and Bun together, and &lt;code&gt;brew upgrade spinuptui&lt;/code&gt; keeps it current. The About panel (&lt;code&gt;?&lt;/code&gt;) recognizes a Homebrew install and shows that command. Installs use the exact dependency versions this release was tested with.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clone Radicle sites.&lt;/strong&gt; Git-deployed Radicle sites now clone properly:
&lt;ul&gt;
&lt;li&gt;Uploads come across from &lt;code&gt;content/uploads&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;After the database import, the site's own deploy script runs on the new server, so the front-end is built (&lt;code&gt;npm ci&lt;/code&gt;, &lt;code&gt;npm run build&lt;/code&gt;, Acorn caches) just as a normal deploy would build it.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clones keep your cron jobs.&lt;/strong&gt; 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 &lt;code&gt;# Carried over from …&lt;/code&gt; comment. Commented-out lines stay commented, SpinupWP's own WordPress cron entry is left to SpinupWP, and a retry never adds a line twice.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clones match the source's settings.&lt;/strong&gt; Page cache, push-to-deploy and the deploy script now come from the source site instead of fixed defaults.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;API headroom in the header.&lt;/strong&gt; &lt;code&gt;API 52/60&lt;/code&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Plugins &amp;amp; themes (&lt;code&gt;e&lt;/code&gt;) no longer shows an empty list on sites with noisy plugins.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;SpinupWP clears a deploy script set through its API&lt;/strong&gt; 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 (&lt;code&gt;v&lt;/code&gt;) &lt;code&gt;g&lt;/code&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.28.0: Multiple SpinupWP accounts</title>
    <link href="https://spinuptui.com/changelog/v0.28.0/"/>
    <id>https://spinuptui.com/changelog/v0.28.0/</id>
    <updated>2026-09-23T20:20:04.000Z</updated>
    <content type="html">&lt;p&gt;If you look after sites in more than one SpinupWP account, say your agency's own and a client who owns theirs, you no longer need separate setups or token juggling. Keep them all in SpinupTUI and switch with one key, always working in exactly one account at a time.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;A&lt;/code&gt; opens Accounts, from any tab.&lt;/strong&gt; Add an account, switch between accounts, rename them, or remove one:
&lt;ul&gt;
&lt;li&gt;A new account's token is checked with SpinupWP before it's saved, and the account slug (used by &lt;code&gt;w&lt;/code&gt;) is pre-filled from the name.&lt;/li&gt;
&lt;li&gt;A help line under the list says what &lt;code&gt;⏎&lt;/code&gt;, &lt;code&gt;e&lt;/code&gt; and &lt;code&gt;x&lt;/code&gt; will do to the selected row.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One account at a time, on purpose.&lt;/strong&gt; There's no merged fleet view, so a reboot or DNS change meant for one client can't land on another's server. The header always shows &lt;code&gt;Account: &amp;lt;name&amp;gt;  A switch&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Switching is a clean reload.&lt;/strong&gt; Servers, sites, events and probes are all fetched fresh for the new account. If a change is still running (a PHP upgrade, DNS edit, database backup, clone, WordPress update…), the switch waits and tells you what's still going.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Each account keeps its own settings:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Per account: its token, DNS provider connections, local-copy links, sudo users and saved Keychain passwords, Uptime Kuma monitor mappings, and cached probes.&lt;/li&gt;
&lt;li&gt;Shared by all accounts: the terminal app, local scan roots, and your Uptime Kuma login.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Removing an account forgets it on this machine:&lt;/strong&gt; its token, Keychain passwords and caches. Nothing changes in SpinupWP, and your local working-copy files stay.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Vanity Site in Stacks.&lt;/strong&gt; Non-WP gains a &lt;strong&gt;Vanity Site&lt;/strong&gt; row for each server's own-hostname site. It's known from the API alone, so these no longer sit under Unknown or unprobed waiting for an SSH probe.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Your existing setup becomes the first account automatically.&lt;/strong&gt; It's labeled with its account slug until you rename it (&lt;code&gt;A&lt;/code&gt; → &lt;code&gt;e&lt;/code&gt;). Its Keychain entries and cache files keep their names, so nothing moves and you won't be asked for sudo passwords again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Back up before upgrading if you might downgrade.&lt;/strong&gt; The first time this version saves a setting, &lt;code&gt;config.json&lt;/code&gt; is rewritten in the new shape, and older versions can't read the token from it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Accounts are stored per machine.&lt;/strong&gt; Add them on each machine where you use SpinupTUI.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commands:&lt;/strong&gt; &lt;code&gt;spinuptui where&lt;/code&gt; lists your accounts, and &lt;code&gt;SPINUPTUI_ACCOUNT=&amp;lt;id&amp;gt;&lt;/code&gt; picks one for a single command. A &lt;code&gt;SPINUPWP_ACCESS_TOKEN&lt;/code&gt; in the environment pins the account, and the overlay tells you so.&lt;/li&gt;
&lt;li&gt;Full details: &lt;a href="https://github.com/mwender/spinupwp-tui/blob/main/docs/multiple-accounts.md"&gt;docs/multiple-accounts.md&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.27.0: Update WordPress core, one site or a whole version group</title>
    <link href="https://spinuptui.com/changelog/v0.27.0/"/>
    <id>https://spinuptui.com/changelog/v0.27.0/</id>
    <updated>2026-09-23T14:56:37.000Z</updated>
    <content type="html">&lt;p&gt;When a WordPress security release lands, you usually want it on every site now, not after a round of manual logins. This release makes that a couple of keystrokes: update core on one site, or on every site running a given version, with a canary site first.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;u&lt;/code&gt; is now Update.&lt;/strong&gt; It opens a menu with &lt;strong&gt;PHP version&lt;/strong&gt; (the flow you know) and &lt;strong&gt;WordPress core&lt;/strong&gt;. The WordPress option checks the site over SSH with wp-cli and lists the versions you can move to, with the newest minor (security) release picked first. After you confirm, it runs &lt;code&gt;wp core update&lt;/code&gt;, then the database upgrade (network-wide on multisite), then reads the version back to verify. It keeps running if you close the overlay, and a toast reports when it's done.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stacks groups WordPress sites by core version.&lt;/strong&gt; Under Standard WP, Bedrock and Radicle, one row per version (&lt;code&gt;└ WP 7.0.2  51&lt;/code&gt;) shows who is still behind. The newest version in the fleet is highlighted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Update a whole version group.&lt;/strong&gt; Press &lt;code&gt;u&lt;/code&gt; on a version row:
&lt;ul&gt;
&lt;li&gt;It checks every site live first, because cached versions go stale as soon as sites update themselves.&lt;/li&gt;
&lt;li&gt;Then it shows a plan you can edit. The default target is the newest release in each site's own line (the low-risk security hotfix); &lt;code&gt;m&lt;/code&gt; switches to the newest release overall, and &lt;code&gt;space&lt;/code&gt; leaves a site out.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;canary&lt;/strong&gt; site always updates alone first; if it fails, nothing else is touched.&lt;/li&gt;
&lt;li&gt;The rest follow up to 4 at a time, never two on the same server, and the run stops after 3 failures. &lt;code&gt;x&lt;/code&gt; stops starting new sites.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Progress shows on the rows.&lt;/strong&gt; A site that's updating shows &lt;code&gt;⠧ → WP 7.1.2&lt;/code&gt;, a failure leaves &lt;code&gt;⬆!&lt;/code&gt;, and sites move into their new version row as they finish.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bedrock and Radicle are included, with a warning.&lt;/strong&gt; The update patches the files on the server, but &lt;code&gt;composer.lock&lt;/code&gt; still pins the old version, so the next &lt;code&gt;composer install&lt;/code&gt; (a deploy, a clone) reverts it. The confirm screen names the pinned version, and bulk plans mark those sites &lt;code&gt;⚙&lt;/code&gt;. Run &lt;code&gt;composer update&lt;/code&gt; and commit the lock to make it stick.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;SpinupWP API errors say why.&lt;/strong&gt; A rejected write used to show only &amp;quot;SpinupWP API error (HTTP 400).&amp;quot; It now includes the API's reason, such as which field it rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Version checks survive noisy plugins.&lt;/strong&gt; Some plugins print PHP deprecation notices to stdout under newer PHP. That output buried wp-cli's update list, so a site two versions behind read as up to date. Core commands now run with plugins and themes unloaded, which also means a plugin that fatals can't block the core update that fixes it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Row versions stay current.&lt;/strong&gt; Any version read by a check or an update now refreshes the version cached from the last &lt;code&gt;d&lt;/code&gt; probe.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Failure toasts are red.&lt;/strong&gt; They used to show a green ✓.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;u&lt;/code&gt; now opens a menu first. Press &lt;code&gt;p&lt;/code&gt; (or Enter) to reach the PHP picker you're used to.&lt;/li&gt;
&lt;li&gt;WordPress core updates use your SSH access as the site user, not the API token, so they work with a read-only token.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.26.1: Launch from inside a site checkout</title>
    <link href="https://spinuptui.com/changelog/v0.26.1/"/>
    <id>https://spinuptui.com/changelog/v0.26.1/</id>
    <updated>2026-09-18T20:55:38.000Z</updated>
    <content type="html">&lt;p&gt;Starting spinuptui from inside a site's checkout, where many of us live all day, could quietly feed that site's own &lt;code&gt;.env&lt;/code&gt; into what the app does. This patch closes that off.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;pull db&lt;/code&gt; works when launched from inside a site's checkout.&lt;/strong&gt; Bun auto-loads the &lt;code&gt;.env&lt;/code&gt; of the directory you start it in, and every process spinuptui spawned inherited it. So a Bedrock site's own &lt;code&gt;DB_*&lt;/code&gt; values reached &lt;code&gt;wp&lt;/code&gt; as real environment variables. Some Bedrock configs then read blank database credentials, and the pre-import backup failed with &lt;code&gt;Access denied for user '&amp;lt;you&amp;gt;'@'localhost' (using password: NO)&lt;/code&gt;. Keys from the launch directory's &lt;code&gt;.env&lt;/code&gt; are now dropped at startup, and every child process gets the cleaned environment. Anything you exported in your shell is kept.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A site's &lt;code&gt;.env&lt;/code&gt; can no longer supply your DNS provider credentials.&lt;/strong&gt; The names are generic, and Bedrock sites commonly keep S3 media keys under &lt;code&gt;AWS_ACCESS_KEY_ID&lt;/code&gt; / &lt;code&gt;AWS_SECRET_ACCESS_KEY&lt;/code&gt;. Launched from such a checkout, spinuptui used them as its Route 53 credentials, silently overriding the ones in config. Provider keys (&lt;code&gt;AWS_*&lt;/code&gt;, &lt;code&gt;CLOUDFLARE_API_TOKEN&lt;/code&gt;, &lt;code&gt;GODADDY_API_*&lt;/code&gt;) from a &lt;code&gt;.env&lt;/code&gt; are now honored only in spinuptui's own project directory. Shell-exported keys work from anywhere, as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;pull db&lt;/code&gt;'s &amp;quot;Access denied&amp;quot; hint points Bedrock and Radicle sites at their &lt;code&gt;.env&lt;/code&gt;.&lt;/strong&gt; It used to blame &lt;code&gt;wp-config.php&lt;/code&gt; for every site, but those stacks keep their database credentials in &lt;code&gt;.env&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;If you were syncing from inside one site's checkout on 0.26.0, it's worth a quick check that the right local database got the import. Depending on a site's Bedrock config, the leaked values could fail outright or, in principle, point &lt;code&gt;wp&lt;/code&gt; at the launch site's database instead.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.26.0: Clone a local working copy from production</title>
    <link href="https://spinuptui.com/changelog/v0.26.0/"/>
    <id>https://spinuptui.com/changelog/v0.26.0/</id>
    <updated>2026-08-26T16:38:56.000Z</updated>
    <content type="html">&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Clone a local working copy from production (&lt;code&gt;L&lt;/code&gt; → &lt;code&gt;c&lt;/code&gt;).&lt;/strong&gt; On a site you have no copy of yet, &lt;code&gt;L&lt;/code&gt; now offers a choice: &lt;code&gt;e&lt;/code&gt; to type in a path you already have, or &lt;code&gt;c&lt;/code&gt; to build the copy. It pulls the code down — &lt;code&gt;git clone&lt;/code&gt; for git-deployed sites, &lt;code&gt;rsync&lt;/code&gt; over SSH for the rest — runs &lt;code&gt;composer install&lt;/code&gt; for Bedrock/Radicle, links the result, and hands off to the DB pull (&lt;code&gt;p&lt;/code&gt;) and media fallback (&lt;code&gt;m&lt;/code&gt;) you already know. Your local database and webserver config are never touched.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The same thing from the command line.&lt;/strong&gt; &lt;code&gt;spinuptui pull files &amp;lt;domain&amp;gt; [path]&lt;/code&gt; and &lt;code&gt;spinuptui pull db &amp;lt;domain&amp;gt; --yes&lt;/code&gt; drive the identical engines with no TUI. Progress goes to stderr, the result to stdout — with &lt;code&gt;--json&lt;/code&gt;, one object, exit code mirroring &lt;code&gt;ok&lt;/code&gt;, and every failure carrying a stable &lt;code&gt;reason&lt;/code&gt; plus a &lt;code&gt;remedy&lt;/code&gt; naming the exact command that fixes it. Built so &amp;quot;pull that site down for local dev&amp;quot; can be handed to an agent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;--server &amp;lt;name&amp;gt;&lt;/code&gt; everywhere a domain is resolved&lt;/strong&gt; (&lt;code&gt;ssh&lt;/code&gt;, &lt;code&gt;ssh-exec&lt;/code&gt;, both &lt;code&gt;pull&lt;/code&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Search gets the full-width Control drawer&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A cloned copy needs its database credentials pointed at your machine before &lt;code&gt;pull db&lt;/code&gt; will run&lt;/strong&gt;, and the app now says so at the point it matters. The file pull brings the site's real &lt;code&gt;wp-config.php&lt;/code&gt; 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: &lt;code&gt;.env&lt;/code&gt; 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.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;wp-content/uploads&lt;/code&gt; is deliberately skipped (that's what the media fallback is for), as are &lt;code&gt;object-cache.php&lt;/code&gt; and &lt;code&gt;advanced-cache.php&lt;/code&gt; — SpinupWP's Redis drop-in doesn't degrade quietly without Redis, it 500s on a cache miss.&lt;/li&gt;
&lt;li&gt;The clone honors the layout rules the rest of the app does: it takes the site's whole files root, so a &lt;code&gt;public/&lt;/code&gt;-style webroot brings &lt;code&gt;wp-config.php&lt;/code&gt; down from the directory above it, and the real webroot is detected on the server rather than inferred from the &lt;code&gt;public_folder&lt;/code&gt; setting.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;K&lt;/code&gt; (grant SSH key) and &lt;code&gt;V&lt;/code&gt; (create/resume vanity site) now work on &lt;strong&gt;server&lt;/strong&gt; results in Search, not just site results — both were advertised in the legend and silently did nothing.&lt;/li&gt;
&lt;li&gt;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 &lt;code&gt;.sql&lt;/code&gt; — empty, or worse, partial — sitting in &lt;code&gt;sql/&lt;/code&gt; looking like a safety net.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.25.0: Pending upgrades are now actionable</title>
    <link href="https://spinuptui.com/changelog/v0.25.0/"/>
    <id>https://spinuptui.com/changelog/v0.25.0/</id>
    <updated>2026-08-12T20:25:09.000Z</updated>
    <content type="html">&lt;p&gt;Server actions no longer leaves a pending SpinupWP platform upgrade as a dead end.&lt;/p&gt;
&lt;h2&gt;Highlights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Server actions surfaces pending SpinupWP upgrades.&lt;/strong&gt; The API only exposes this as a flag — no title, no description, no endpoint to run it — so the overlay (&lt;code&gt;a&lt;/code&gt;) now shows a banner explaining that, with &lt;code&gt;w&lt;/code&gt; to jump straight to the upgrade in the SpinupWP web app.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;App version on the splash screen&lt;/strong&gt;, shown while the first batch of data loads.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The reboot-pending detail line now shows the real reason when the SSH probe fails (e.g. an auth error), instead of a generic &amp;quot;couldn't read detail over SSH&amp;quot; message.&lt;/li&gt;
&lt;li&gt;Long banner text now wraps across lines instead of overflowing the panel border.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.24.4: the toast crash is actually fixed now</title>
    <link href="https://spinuptui.com/changelog/v0.24.4/"/>
    <id>https://spinuptui.com/changelog/v0.24.4/</id>
    <updated>2026-08-06T19:08:50.000Z</updated>
    <content type="html">&lt;p&gt;If &lt;code&gt;v0.24.2&lt;/code&gt;/&lt;code&gt;v0.24.3&lt;/code&gt; still had you crashing on startup, this is the real fix.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Startup crash: &lt;code&gt;Unknown component type: toaster&lt;/code&gt;, for real this time.&lt;/strong&gt; The previous two patches tried to fix this by pinning/overriding the opentui version we depend on, but that only works for a local project install — it has no effect on a global install (&lt;code&gt;bun add -g&lt;/code&gt;, &lt;code&gt;npm install -g&lt;/code&gt;), which is how everyone actually runs spinuptui. The real problem was the toast library itself: it's stuck on a peer-dependency range from opentui's very early days, and no version pin on our side could fix how it resolves its own dependencies downstream. Every toast this app ever shows is a single-line success message, so the external toast library is gone — replaced with a small first-party implementation with no external dependency and no peer-dependency surface left to break on a future update.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.24.3: fix a startup crash from a duplicate opentui install</title>
    <link href="https://spinuptui.com/changelog/v0.24.3/"/>
    <id>https://spinuptui.com/changelog/v0.24.3/</id>
    <updated>2026-08-06T18:12:15.000Z</updated>
    <content type="html">&lt;p&gt;If &lt;code&gt;v0.24.2&lt;/code&gt; left you crashing on startup with &lt;code&gt;Unknown component type: toaster&lt;/code&gt;, this fixes it.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Startup crash: &lt;code&gt;Unknown component type: toaster&lt;/code&gt;.&lt;/strong&gt; The &lt;code&gt;0.24.2&lt;/code&gt; fix pinned &lt;code&gt;@opentui/core&lt;/code&gt;/&lt;code&gt;@opentui/react&lt;/code&gt;, which resolved a toast-dismissal crash but exposed a second bug: the toast library's peer-dependency range is ancient (predates the current &lt;code&gt;0.4.x&lt;/code&gt; line) and our pinned version can't satisfy it, so a fresh install ended up with a second, independent nested copy of &lt;code&gt;@opentui/react&lt;/code&gt; alongside ours. The toast library registers its custom &lt;code&gt;&amp;lt;toaster&amp;gt;&lt;/code&gt; component on that nested copy, which our app's copy never sees — crashing the moment the toast area tries to mount. &lt;code&gt;package.json&lt;/code&gt; now forces a single deduped install everywhere via &lt;code&gt;overrides&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.24.2: fix toast crash from an @opentui/core dependency drift</title>
    <link href="https://spinuptui.com/changelog/v0.24.2/"/>
    <id>https://spinuptui.com/changelog/v0.24.2/</id>
    <updated>2026-08-06T15:35:06.000Z</updated>
    <content type="html">&lt;p&gt;Fixes a crash some of you may have hit on a fresh install: dismissing a toast (PHP upgrade, reboot, cache purge, etc.) could throw &lt;code&gt;remove expects a renderable child object&lt;/code&gt; and take the app down.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Toast dismissal crash.&lt;/strong&gt; &lt;code&gt;@opentui/core&lt;/code&gt; changed the signature of an internal method it uses starting at &lt;code&gt;0.4.3&lt;/code&gt;, and the toast library spinuptui depends on hasn't published a matching fix yet. Our dependency range let a fresh install with no lockfile — most likely on a machine installing spinuptui for the first time — resolve onto that broken later patch. &lt;code&gt;@opentui/core&lt;/code&gt; and &lt;code&gt;@opentui/react&lt;/code&gt; are now pinned to the last known-good patch (&lt;code&gt;0.4.2&lt;/code&gt;) until the toast library ships a compatible release.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.24.1: fix bun update -g silently not updating</title>
    <link href="https://spinuptui.com/changelog/v0.24.1/"/>
    <id>https://spinuptui.com/changelog/v0.24.1/</id>
    <updated>2026-08-06T14:44:18.000Z</updated>
    <content type="html">&lt;p&gt;&lt;code&gt;bun update -g spinuptui&lt;/code&gt; &lt;em&gt;not updating for you?&lt;/em&gt; I just figured out why...since we're at the pre-release stage (i.e. not yet to &lt;code&gt;v1.0.0&lt;/code&gt;), that command will silently fail. To pull the latest pre-release version, you must run &lt;code&gt;bun add -g spinuptui@latest&lt;/code&gt;. More details below:&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;bun update -g spinuptui&lt;/code&gt; no longer silently fails to update.&lt;/strong&gt; While spinuptui is pre-1.0, a package-manager global install records a caret version range (e.g. &lt;code&gt;^0.22.2&lt;/code&gt;) that, under semver, only matches patch releases — every later minor release fell outside it, so &lt;code&gt;update -g&lt;/code&gt; reported success without actually updating anything. The documented and in-app update command (Help/About panel, README) is now &lt;code&gt;bun add -g spinuptui@latest&lt;/code&gt;, which always pulls the true latest version.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.24.0: Pull prod. DB is discoverable even when local sync is off</title>
    <link href="https://spinuptui.com/changelog/v0.24.0/"/>
    <id>https://spinuptui.com/changelog/v0.24.0/</id>
    <updated>2026-07-15T17:00:27.000Z</updated>
    <content type="html">&lt;h2&gt;Added&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;p&lt;/code&gt; (Pull prod. DB) is now discoverable even when &lt;code&gt;localSync&lt;/code&gt; is off.&lt;/strong&gt; Previously the Site Control legend hid the entry entirely until &lt;code&gt;localSync&lt;/code&gt; was enabled in config — the only one of &lt;code&gt;p&lt;/code&gt;'s three preconditions (WordPress, linked copy, &lt;code&gt;localSync&lt;/code&gt;) that hid the entry instead of flashing a message on press. Now &lt;code&gt;p&lt;/code&gt; always shows for WordPress sites; pressing it with &lt;code&gt;localSync&lt;/code&gt; off opens an in-app &amp;quot;Enable local sync?&amp;quot; confirm instead. Confirming just saves the setting — you press &lt;code&gt;p&lt;/code&gt; again afterward to actually pull, so the destructive action itself stays behind two deliberate presses, same as before.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.23.0: Radicle sites are now detected and labeled</title>
    <link href="https://spinuptui.com/changelog/v0.23.0/"/>
    <id>https://spinuptui.com/changelog/v0.23.0/</id>
    <updated>2026-07-15T14:49:43.000Z</updated>
    <content type="html">&lt;p&gt;Radicle (Roots' Bedrock+Sage+Acorn+Trellis starter for WordPress) is now its own detected stack, instead of being misclassified as Bedrock.&lt;/p&gt;
&lt;h2&gt;Added&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Radicle sites are now detected and labeled as their own stack.&lt;/strong&gt; Radicle shares Bedrock's &lt;code&gt;roots/bedrock-autoloader&lt;/code&gt; dependency, which was tripping a naive &lt;code&gt;roots/bedrock&lt;/code&gt; string match; detection now keys off &lt;code&gt;roots/acorn&lt;/code&gt; instead — the package that actually makes a site Radicle. Radicle only surfaces via the on-demand SSH probe (&lt;code&gt;f&lt;/code&gt; in the Servers/Search tabs, &lt;code&gt;d&lt;/code&gt;/&lt;code&gt;D&lt;/code&gt; in Stacks) — its &lt;code&gt;/public/&lt;/code&gt; webroot alone is indistinguishable from a hardened Standard-WP &lt;code&gt;/public/&lt;/code&gt; layout. DB backup/sync, plugin/theme inventory, and local working-copy linking already worked on Radicle sites (their path detection was already stack-agnostic); this release just adds the missing name. Clone-wizard support for Radicle is a separate, not-yet-built follow-up.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A few README/docs mentions of &lt;code&gt;p&lt;/code&gt; (plugins &amp;amp; themes) and &lt;code&gt;m&lt;/code&gt; (monitoring) that slipped through the previous release's key-unification work — corrected to &lt;code&gt;e&lt;/code&gt; and &lt;code&gt;M&lt;/code&gt;, and scope notes broadened from &amp;quot;Search tab&amp;quot; to &amp;quot;Servers / Search tabs&amp;quot; where applicable.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <title>SpinupTUI v0.22.3: Site Control keys work the same in Servers and Search</title>
    <link href="https://spinuptui.com/changelog/v0.22.3/"/>
    <id>https://spinuptui.com/changelog/v0.22.3/</id>
    <updated>2026-07-15T14:30:14.000Z</updated>
    <content type="html">&lt;p&gt;A fix-up release building on last week's Servers-tab Control strip work.&lt;/p&gt;
&lt;h2&gt;Fixed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;p&lt;/code&gt; actually pulls the production DB in the Servers tab now.&lt;/strong&gt; The Site Control legend labeled it &amp;quot;Pull prod. DB,&amp;quot; but pressing it opened the plugins/themes inventory instead — the DB-pull action was never wired up in that tab at all. Plugins/themes moved to &lt;code&gt;e&lt;/code&gt; in both the Servers and Search tabs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;d&lt;/code&gt;, &lt;code&gt;m&lt;/code&gt;, &lt;code&gt;a&lt;/code&gt;, &lt;code&gt;K&lt;/code&gt;, and &lt;code&gt;f&lt;/code&gt; now behave the same in the Servers tab and Search.&lt;/strong&gt; The shared Site Control legend was written against Search's key bindings, and the Servers tab had silently diverged on several of them: &lt;code&gt;d&lt;/code&gt; ran a stack-identify probe instead of a DB backup, &lt;code&gt;m&lt;/code&gt; had no media-fallback binding at all, &lt;code&gt;a&lt;/code&gt; (reboot/restart) silently did nothing with a site focused, and &lt;code&gt;K&lt;/code&gt; (grant SSH key) was listed in Search's legend but never actually wired up there. The stack-identify probe now lives on &lt;code&gt;f&lt;/code&gt; in both tabs.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
</feed>
