tuandClaude Opus 4.7
efd3f9d5ae
Dashboard now reachable across the internet: browser calls /api/dashboard/* same-origin, PHP forwards to OUMTA_DASHBOARD_URL (configurable via env, with docker-compose defaults pointing at host.docker.internal:8085). Keeps the bearer token server-side and lets the dashboard live on a private network. Plumbing bits: polling indicator now green (no reason to look anxious about a healthy poll loop), and the support plugin returns 200 pulled=0 when its relay isn't configured instead of flooding the network tab with 502s on every background tick. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
oumta-dashboard plugin
Fullscreen view for the Oumta cluster dashboard (Go backend in oumta-dashboard/).
Open
- Oumta button in the hyprcrd top bar (next to Tasks)
window._oumtaToggle()from the console / other plugins
Close with ESC or the × button.
Views
- Overview — cluster state, workload counts, attention list
- Workloads — filterable table (name, state, replicas, cpu/mem, image, reason)
- Timeline — event stream; clicking a workload filters down to its own events
Namespaces
Tab row at the top. Currently two mocks (oumta-dev, oumta-beta). Real list comes from the backend once /api/namespaces exists.
Configuration
Hardwired at the top of oumta-dashboard.js in the CONFIG block:
- baseUrl — where the Oumta Go backend is reachable (default
http://localhost:8085). - authToken — optional, sent as
Authorization: Bearer …when non-empty. - pollIntervalSec — polling fallback cadence when SSE is unavailable. Default 15 s.
No UI settings panel: the dashboard only runs against one specific deployment, so exposing these as editable fields would be noise.
State today
Everything is mocked. The live indicator in the top right shows polling once the overlay is open, but no real HTTP call fires yet. See TODO.md for the integration plan.
Disabling
Add "oumta-dashboard" to the disabled array in data/plugins.json.