omnyserver_web v0.2.0 — the dashboard

Live at → https://omnygrid.github.io/omnyserver/

The dashboard: a browser you can run a fleet from. A static, installable PWA that operates an OmnyServer Hub with no backend of its own — it is the Hub's REST API, seen. Served from GitHub Pages, and equally servable from the Hub itself.

Tagged separately from the server (v0.14.0) because it ships from the same repo but versions on its own — a Pages deploy is gated on a bump to this version, so a server-only release does not redeploy it.

The fleet

Log in against a Hub URL with a grant, validated up front by whoami, so a bad token fails at the door rather than on the first thing you try to do — and the roles it returns decide what the UI offers. Then: every node, online and off, searchable and filterable by label; per-node detail with live CPU, memory, per-device storage and a process table; a metrics chart drawn from samples the Hub had been persisting on every heartbeat since long before anything read them back; and an activity feed that is a console over SSE rather than a poll.

Control

Restart, shutdown, update, run a formula, apply a preset — behind confirmation and behind the role that permits it. Act on one node, on a label, or on all of them, with a per-node result matrix. Declare desired state and see the drift. Long operations run asynchronously, so an install that outlives a request no longer times out in the browser.

The shell

Open a shell on any node, in the dashboard. The terminal — xterm view, PTY bridge, mobile fit engine, accessory bar — is imported from omnyshell_web rather than rebuilt, and drives the OmnyShell broker the Hub hosts on the same port. One Hub, one certificate, one login.

Requires

omnyserver 0.14.0 · omnyshell_web 1.15.0 · omnyhub 1.6.0

Full notes: omnyserver_web/CHANGELOG.md