Dashboard
Use the Zectre web console to inspect clusters, applications, deployments, and tasks.
Purpose
The dashboard is the operations surface for Zectre: it drives the same platform capabilities as the CLI (projects, deployments, tasks, org context) through a browser UI.
What you typically do here
- Clusters & nodes — See registered agents, capacity signals, and connectivity context.
- Applications & deployments — Track what was deployed, when, and which revision is live.
- Tasks — Inspect running (or failed) task instances, ports, and health.
- Settings / orgs — When catalog auth is enabled, manage organization and sign-in flows tied to GitHub OAuth.
Environment variables
Behavior depends on how you run the SPA. Copy zectre-platform/dashboard/.env.example from the platform repository you deploy against and adjust.
Catalog mode (VITE_CATALOG_URL set): After sign-in, platform API requests use the catalog-selected target’s api_base_url, not VITE_API_URL. The catalog supplies cluster/API endpoints per context.
Without catalog: The app uses VITE_API_URL (or same-origin /api/v1 when unset), optionally with VITE_ZECTRE_API_KEY for automation-style access.
Local development helpers (see .env.example): VITE_LOCAL_CATALOG_SHELL, VITE_MOCK_CATALOG_SHELL, VITE_PLATFORM_DOMAIN, VITE_PLATFORM_BASE_URL, VITE_JWT_AUDIENCE, etc.
Rebuild the dashboard after changing env. Align JWT issuer/audience with the cluster API — Auth & catalog.
CLI overlap
Many workflows you see in the UI are also available from zectre for scripting and CI — see Commands and Linking & projects. The two surfaces are not guaranteed to be 1:1 for every future feature.