Skip to main content

Web console

The API serves a zero-dependency web console at:

https://<pagifier-api>/console

Paste a scoped API token once (kept in the browser's local storage). The applications tab lists what that token may see:

  • live phase (Available / Deploying / Failed / …) and the deployed URL;
  • a canary badge with the current traffic weight during canary rollouts, and the active color for blue/green apps;
  • expandable per-application release history: release id, artifact digest, image, and timestamp.

The Git setup tab is the friendly on-ramp for a normal single-repository service. It creates a service-token connection, renders the single-repo-service control manifest, shows the one-time webhook secret, and activates the pipeline after you commit the file. Multi-repo, GitHub App, and custom-provider setup stays in the API for now.

The console is a single embedded HTML page — no build step, no separate deployment, no additional authentication surface. Data calls use the same bearer-token API as every other client, so the console can never do more than the token's role and resource scope allow. A strict Content-Security-Policy confines the page to same-origin API calls.

For anything the console doesn't show, the REST API is the source of truth; for alerting, use the deploy-notification webhook and Prometheus metrics rather than watching the console.