fix(deploy): reuse shared server n8n

This commit is contained in:
NuklearRabbit
2026-08-02 03:56:17 +02:00
parent 686b62f592
commit 1f292e14bb
12 changed files with 234 additions and 61 deletions
+4 -2
View File
@@ -66,8 +66,10 @@ The same widths are automated in `frontend/e2e/ui-redesign.spec.ts`.
- Authenticated network verification through the deployed web proxy returned HTTP 200
for dashboard, vehicles, active booking, open quality issues, knowledge status,
workflows and audit.
- Container verification: PostgreSQL and API healthy, web HTTP 200, n8n `/healthz`
returned `{"status":"ok"}`. Existing database and n8n volumes were preserved.
- Container verification: PostgreSQL and API healthy, web HTTP 200, and the server's
existing n8n on port 5678 returned healthy. No second MobilityOps n8n container is
running. A synthetic return completed the shared-n8n callback on attempt 1 and the demo
was reset to its deterministic start state.
## Performance choices