fix(deploy): run Z API on port 3100 in production to avoid Gitea conflict
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m14s
CI/CD Pipeline / Security Scanning (push) Successful in 2m27s
CI/CD Pipeline / Lint and Format (push) Failing after 45s
CI/CD Pipeline / Terraform Validation (push) Failing after 22s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 25s
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 37s
Validation / validate-genesis (push) Successful in 28s
Validation / validate-terraform (push) Failing after 25s
Validation / validate-kubernetes (push) Failing after 10s
Validation / validate-smart-contracts (push) Failing after 11s
Validation / validate-security (push) Failing after 1m16s
Validation / validate-documentation (push) Failing after 18s
Verify Deployment / Verify Deployment (push) Failing after 55s

Production server binds Gitea on :3000, so token-aggregation now uses
:3100 with a dedicated production env profile and nginx upstream.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-07-07 07:41:20 -07:00
parent a2db92f3cb
commit 1cce8ed08f
4 changed files with 33 additions and 6 deletions

View File

@@ -7,7 +7,7 @@ upstream z_ecosystem_frontend {
}
upstream z_ecosystem_api {
server 127.0.0.1:3000;
server 127.0.0.1:3100;
}
upstream z_ecosystem_settlement {