ai-workspace-services/portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5c84390b90
portal/docs/en/deployment.md
Haitao Pan 5c84390b90 fix(console): add account api fallback proxy
2026-04-01 16:20:41 +08:00

2.3 KiB
Raw Blame History

Deployment

Production Baseline

  • Runtime: Caddy + Docker Compose
  • Deploy host: root@cn-console.svc.plus
  • Domains:
    • cn-console.svc.plus
    • cn-console.onwalk.net
  • Frontend release workflow: .github/workflows/service_release_frontend-deploy.yml

Operating Model

The frontend is built in GitHub Actions and shipped as a prebuilt linux/amd64 image. The host only pulls the image and starts containers; it does not build locally.

yarn prebuild now generates only console-owned marketing artifacts. /docs and /blogs no longer bundle knowledge/ or synced markdown content into the frontend image. Those routes fetch rendered content from docs.svc.plus at request time through the server-side docsServiceClient.

The stack is static-first:

  • Caddy serves /_next/static/* and public assets from a shared read-only volume.
  • The Next.js standalone container serves dynamic HTML, auth endpoints, and API proxy routes. Static assets and hashed CSS/JS files are extracted by the frontend-assets helper task, so the runtime no longer needs to compile anything on the single-node host.
  • docs.svc.plus is the source of truth for rendered docs/blog pages; the browser does not call it directly.

Releases are orchestrated through .github/workflows/service_release_frontend-deploy.yml. That workflow builds/pushes the image, renders .env.runtime including DOCS_SERVICE_URL / DOCS_SERVICE_INTERNAL_URL, and ships docker-compose.yml, Caddyfile, and the runtime env file to the host. The control-plane workflow .github/workflows/service_release_apiserver-deploy.yml then updates Cloudflare DNS for the release domain (via scripts/github-actions/update-release-dns.sh) so cn-console.svc.plus and the redirected alias cn-console.onwalk.net point at the new environment.

This baseline is intentional for the weak-IO single-node host root@cn-console.svc.plus. No images are built on the target machine, keeping the deployment lightweight: the host only logs into GHCR, pulls the dashboard image, extracts assets into frontend_static, and starts dashboard plus caddy containers via docker compose.

docs.svc.plus is now the dedicated docs/blog service for the frontend delivery path.

Related Docs

  • usage/deployment.md
  • governance/release-process.md
  • development/dev-setup.md