Skip to main content

v0 / Vercel: Report Deploy and Cockpit (Part J)

Target Audience: Editorial Team (v0), IT (one-time Vercel)

Workflow (v0-first)​

Editorial Team in v0 (Instructions A–I + D)
        │
        ├── Content → MCP/content_push → Cockpit (SSOT)
        │
        └── Deploy on Vercel
                 │
                 ▼
        POST /api/cockpit-register (Vercel)
                 │
                 ▼
        Cockpit saves staging/live URLs (Website) or signage / companion
                 │
                 └── Publish (v0-Chat or Cockpit) → Revalidate → Live

Live Operation: Changes in v0-Chat or Cockpit — both write to Cockpit; frontends read the same API.

For Editorial Team (v0 Instruction "Cockpit J")​

After the first Vercel deploy in the chat:

“Report this deploy URL to Cockpit (Part J): cockpit_register_frontend_deployment with channel website.”

Alternatively, IT can set up a Deploy Hook — then nothing manually.

Instruction text to copy: center-website-v0-api-ready-to-go — Part J

For IT​

Recommended (Team Setup): Set up v0 Team Template — Shared Env once, per Center only Token + Slug.

Classic / Detailed: v0-Website A–Z — Section F3

In brief (per Center, if the template is ready):

  1. Dashboard → Frontend Channels (v0) → Generate Register Token
  2. Vercel Project Env: COCKPIT_REGISTER_TOKEN, COCKPIT_CENTER_SLUG, NEXT_PUBLIC_DASHBOARD_URL (like API base)
  3. Team Shared Env (link each project): COCKPIT_DASHBOARD_URL, REVALIDATION_SECRET, COCKPIT_FRONTEND_CHANNEL
  4. postbuild or Deploy Hook → POST …/api/cockpit-register (included in the template)

API (Developer)​

RouteAuthBody
POST /api/public/frontend-deployments/registerX-Cockpit-Register-Token: frt_… or Bearer AgencyOS{ channel, origin, environment?, source? }
POST /api/agencyos/v1/centers/{centerId}/frontend-deployments/registerBearer AgencyOS{ channel, origin, environment?, source? }

environment: preview (Staging, *.vercel.app) or production (Live). Default: from origin or Vercel VERCEL_ENV during the hook. Go-Live/DNS only for custom domains — not for preview URLs.

Security: The register token is per Center — no secret in the browser. It only overwrites the URL of the selected channel; does not delete any other data.

MCP: cockpit_register_frontend_deployment

Migration (Live DB)​

Additive, no data loss:

cd packages/database
npx prisma db execute --file migrations/20260521140000_add_frontend_deployment_register_SAFE.sql --schema schema.prisma
npx prisma generate

See Also​

Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/digital-signage/v0-deploy-cockpit-register