Skip to content

v0.9.0 — Create, connect & clone servers

Choose a tag to compare

@mwender mwender released this 30 Jun 15:28
· 191 commits to main since this release
b600098

Stand up a server, connect it end to end, and clone a whole server to a new one — all from the terminal — plus the first privileged writes the SpinupWP API can't do.

Highlights

  • Clone a server (C). A guided wizard clones one or more of a server's sites onto a new/existing destination — plan + size, provision/pick the dest, pull each site server-to-server (Standard WP and Bedrock), verify against the source, and repoint DNS only when you say so. Runs in the background.
  • Create & connect servers (c / V). Provision a server priced from the provider catalog (DigitalOcean / Vultr / Linode / Hetzner), then connect a 0-site box end to end with a vanity site (DNS → site → HTTPS → SSH-key handoff).
  • Privileged writes over SSH: sudo (S) + SSH keys (K). Connect sudo for the session, then grant/revoke your personal key and/or Spinup's dedicated machine key — one site or every site on the server.
  • Save your sudo password to the macOS Keychain (opt-in). Auto-unlocks sudo next session; the password lives only in the Keychain + memory, never config.json.
  • Completion toasts. PHP upgrades and server reboots/restarts raise a toast when they finish.

Notes

  • The SSH actions (sudo, key grant, clone pull) use your own SSH access, not the API token. Create / clone / PHP / reboot need a Read/Write token.
  • Clone never touches DNS until the final cutover step, which you trigger.
  • The Keychain save is opt-in and macOS-only.

Update: git pull in your checkout, then bun install — this release adds a dependency (@opentui-ui/toast), so a pull alone isn't enough. The global spinup symlink picks up the new code immediately.

Full changelog: v0.8.0...v0.9.0