Mike Swanson
43a9432b81
All checks were successful
React + Vite + TypeScript SPA: scaffold, operations-terminal design system, Bearer-token auth, and the Machines view. - Design system: OKLCH-tinted dark theme (ink-slate + signal-cyan), Hanken Grotesk + JetBrains Mono, status-color language (online/offline/granted/pending/denied/not_required), motion with prefers-reduced-motion honored. - Auth: token in sessionStorage via ref (never React state), protected routes, 401 session teardown, admin-gated per-agent-key UI. - Machines view: data table (sticky header, keyboard-activated rows, skeleton loading, actionable empty/error states), non-blocking detail drawer, delete confirm, admin key management with copy-once reveal. - UI primitives: Modal (focus trap + inert + portal + dialogStack), Drawer, Table, Badge/StatusDot, toast, states. - Typed API client normalizing the two error-envelope shapes. Passed Code Review (no blockers), impeccable critique-and-polish, and local gates (tsc/lint/build green). Dev-only Vite proxy to :3002. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
13 lines
585 B
Plaintext
13 lines
585 B
Plaintext
# GuruConnect dashboard — environment.
|
|
# Copy to `.env.local` for local overrides (gitignored via `*.local`).
|
|
|
|
# Base URL for the GuruConnect API. Leave UNSET to use same-origin (the
|
|
# production default — the dashboard is served by the GC server itself).
|
|
#
|
|
# In `npm run dev`, leave this unset too: Vite proxies `/api` and `/ws` to the
|
|
# local GC server (see vite.config.ts), so same-origin requests just work.
|
|
#
|
|
# Set it only to point the dashboard at a *different* host (e.g. a remote
|
|
# server while developing the UI locally):
|
|
# VITE_API_URL=https://connect.azcomputerguru.com
|