| Filename | Latest commit message | Latest commit date |
|---|---|---|
Frontend for the BE-4 snapshot (#1702): GET /api/matrix-accounts now returns per-account `live` + `user_id` and a top-level `as_of_unix`. Render a 3-state dot instead of the v1 token-present-only one: - green (live + container running) — online - amber (live + container DOWN) — stale: the page already loads /api/state containers, so cross-reference running state; a container that's down means the daemon is down, so a "live" snapshot there is stale - amber (token_present + !live) — provisioned but offline - grey (no token) — not provisioned The daemon rewrites its snapshot only on (re)start, so `as_of_unix` is "live as of", not a heartbeat — surfaced as a tooltip. We deliberately do NOT dim a green purely on snapshot age (an old as_of is ambiguous: stable uptime vs dead daemon); the container cross-ref catches the definitive down case, and true daemon-up-but-client-dead detection is the daemon-heartbeat follow-up. user_id is shown next to the account name. When `live` is absent (v1 backend not yet deployed) the dot falls back to the token-present rendering, so this is safe to ship independent of the backend deploy. FE half of #1702 BE-4; pairs with the backend PR. |
||
| .. | ||
| packages | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
hyperhive frontend
npm workspaces project for the hyperhive browser-facing assets:
packages/shared/— shared modules used by both surfaces (terminal pane, Catppuccin palette + body typography).packages/dashboard/— the hive-c0re dashboard SPA.packages/agent/— the per-container web UI (default agent page, stats, screen).
Build
npm install # one-off; uses the checked-in package-lock.json
npm run build # builds every workspace into packages/*/dist/
The Rust binaries serve packages/dashboard/dist/ and
packages/agent/dist/ via tower_http::ServeDir at runtime; the
build derivation is wired up in nix/modules/frontend.nix. Per-agent
additions are layered on top of the default agent dist via the
hyperhive.frontend.extraFiles option in agent.nix.
Why npm + esbuild
- Hermetic: dependencies vendored via the checked-in lockfile;
buildNpmPackagein nix uses it as the source-of-truth so the output is reproducible without network access at build time. - esbuild: vanilla-JS bundler, no framework runtime overhead.
Each workspace's
build.mjsis ~30 lines. - Single-PR migration: see issue #273 for the design proposal and the four-commit shape (npm scaffold → nix derivations → container plumbing → Rust cutover).