KB-290B
05 — UI Deploy Path
2 min read Revision 1
05 — UI Deploy Path (Phase E)
Not deployed this run (deploy follows PR merge; no agent git/deploy authority over the public diverged repo).
Deployment method (observed live)
- Nuxt runs as container
incomex-nuxt(imagenuxt-ssr-local:s174, internal port 8080, fronted byincomex-nginxon 443/80). Currently Up 11h, healthy. - Source repo on box:
/opt/incomex/docker/nuxt-repo/web.
OPERATOR DEPLOY PACKET (after PR merge)
Steps for the operator, run on contabo in the nuxt repo directory:
- Switch to
main, pull the merged remote main onto the deploy tree. - Rebuild the
nuxtservice image using the existing compose build pipeline underinfra/docker. - Bring the
nuxtservice back up detached.
(Use the project's standard compose build + up for the nuxt service; do not hand-edit images.)
SMOKE TESTS (post-deploy)
- GET
/knowledge/process-axis→ expect HTTP 200. - GET
/api/process-axis/overview→ expect read-only JSON overview, no 5xx. - Page renders the Process/Trigger governance tiles; values reconcile with
v_total_final_acceptance_scorecard. - Confirm NO write side-effects — page + API are read-only rpQuery pass-through.
Rollback
Redeploy the prior image tag (nuxt-ssr-local:s174) or the previous main.
Caution
Local main is ahead17/behind13 of origin/main — reconcile the deploy tree to the merged remote main BEFORE building, so the deploy reflects the reviewed PR rather than local divergence.
Verdict
Deploy path FINAL — exact post-merge packet + smoke tests ready. Gated on Phase D push + merge.