Changelog

v0.28.0

Multiple SpinupWP accounts · September 23, 2026

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.

Highlights

  • A opens Accounts, from any tab. Add an account, switch between accounts, rename them, or remove one:
    • A new account's token is checked with SpinupWP before it's saved, and the account slug (used by w) is pre-filled from the name.
    • A help line under the list says what ⏎, e and x will do to the selected row.
  • One account at a time, on purpose. 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 Account: <name> A switch.
  • Switching is a clean reload. 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.
  • Each account keeps its own settings:
    • Per account: its token, DNS provider connections, local-copy links, sudo users and saved Keychain passwords, Uptime Kuma monitor mappings, and cached probes.
    • Shared by all accounts: the terminal app, local scan roots, and your Uptime Kuma login.
  • Removing an account forgets it on this machine: its token, Keychain passwords and caches. Nothing changes in SpinupWP, and your local working-copy files stay.
  • Vanity Site in Stacks. Non-WP gains a Vanity Site 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.

Notes

  • Your existing setup becomes the first account automatically. It's labeled with its account slug until you rename it (A → e). Its Keychain entries and cache files keep their names, so nothing moves and you won't be asked for sudo passwords again.
  • Back up before upgrading if you might downgrade. The first time this version saves a setting, config.json is rewritten in the new shape, and older versions can't read the token from it.
  • Accounts are stored per machine. Add them on each machine where you use SpinupTUI.
  • Commands: spinuptui where lists your accounts, and SPINUPTUI_ACCOUNT=<id> picks one for a single command. A SPINUPWP_ACCESS_TOKEN in the environment pins the account, and the overlay tells you so.
  • Full details: docs/multiple-accounts.md

View on GitHub →