Changelog

v0.4.0

Server actions: reboot + service restarts · June 18, 2026

The second write action: reboot a server or restart a service, right from the dashboard.

Highlights

  • Server actions — press a on a server (Servers tab, or a result in Search) to reboot it (POST /servers/{id}/reboot) or restart a service: Nginx / PHP-FPM / MySQL / Redis (POST /servers/{id}/services/{svc}/restart). Pick → confirm → the event is tracked to completion. Like PHP upgrades, it runs in the background: close the overlay with Esc and the server's row keeps a spinner until it settles.
  • Reboot is the careful one — its confirmation calls out that it takes the whole server down briefly (every site on it); a service restart is a brief blip.
  • Reboot visibility — servers needing a reboot show a ↻rbt badge in the Servers list and in Search results (and were already on the Dashboard's "Needs attention" panel).
  • Why a reboot is pending — the SpinupWP API exposes only a reboot_required boolean with no reason, so the overlay reads Ubuntu's /var/run/reboot-required (+ .pkgs) over SSH (read-only, reusing the health-view connection) and shows the pending packages — typically a kernel/security update. Labeled as OS-level context, not as SpinupWP's internal logic (a fleet-wide check confirmed the boolean tracks that file 1:1).

Notes

  • These actions need a SpinupWP Read/Write token; with a Read Only token they return a clear "token is read-only" message and nothing changes.
  • Reuses the write scaffolding introduced in v0.3.0 (mutate / event polling / confirm overlay).

View on GitHub →