Web dashboard

The server ships a small ops dashboard at /ui — a single self-contained page (vanilla JS, no build step, no CDN) that talks to the same REST + WebSocket API.

http://HOST:8765/ui

It shows:

  • a stats header (GET /v1/stats) — jobs by status, tasks in flight, live worker count;

  • a jobs table filterable by status/name, with per-job task counts, best metric and a cancel button; expand a row for its ranking and recent events;

  • a workers table with slots, labels and each worker’s nirs4all-cluster version (flagged when it diverges from the server);

  • a live event feed over the global stream GET /v1/events/stream.

If the server has a token, paste it into the dashboard’s token field (stored in the browser’s localStorage); it is sent as Authorization: Bearer … on requests and as ?token= on the WebSocket. With no token (dev mode) the dashboard works as-is.

Note

This is a deliberately minimal operations view for the queue itself (in the spirit of Flower / RQ-dashboard) — distinct from nirs4all-studio, which is the full data-science application. For cross-origin browser access to the API, enable CORS with --cors-origin.