gitea-admin/CASAN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add production deployment handoff controls

Browse Source
This commit is contained in:
thanhnv
2026-07-10 16:41:14 +09:00
parent 7cea023dce
commit aa284e9bd4
14 changed files with 408 additions and 109 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/casan-control-panel/README.md
+5 -5
View File
@@ -117,7 +117,6 @@ npm run console:build # backend tsc + frontend typecheck/vite build
## Production-Like Smoke
```bash
docker compose -f docker-compose.control-panel.yml config
bash packages/casan-control-panel/scripts/local-prod-smoke.sh
```
@@ -131,12 +130,13 @@ asserts the Command Center returns all nine widgets with provenance envelopes an
therefore emits both `CP_LOCAL_SMOKE_PASS ...` and
`CP_MANAGED_SMOKE_PASS actor=oidc-ops role=org-admin widgets=9`.
Managed production readiness, once the host has real TLS files and an enterprise OIDC
env file:
Managed production readiness is intentionally a stronger, fail-closed contract: it
requires a DNS-matching TLS certificate, enterprise OIDC, non-dev Vault Transit,
an actual S3 Object Lock COMPLIANCE write, and CI-attested digest-pinned images.
Follow [the Linux handoff guide](../../infra/production/README.md), then run:
```bash
CASAN_CP_TLS_DIR=/opt/casan-control-panel/tls \
CASAN_CP_OAUTH_ENV=/opt/casan-control-panel/oauth2-proxy.env \
CASAN_CP_PROD_ENV=infra/production/casan-prod.env \
bash packages/casan-control-panel/scripts/prod-readiness-check.sh
```