fix: [nomad-step-5] S5-fix-7 — staging port 80 collides with edge; staging should use dynamic port (#1018)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/push/nomad-validate Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
ci/woodpecker/pr/nomad-validate Pipeline was successful
ci/woodpecker/pr/secret-scan Pipeline was successful

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude 2026-04-18 13:39:30 +00:00
parent a35d6e7848
commit e6dcad143d
3 changed files with 63 additions and 5 deletions

View file

@ -10,8 +10,8 @@
# served to staging environment users.
#
# Network:
# No external port exposed edge proxy routes to it internally.
# Service discovery via Nomad native provider for internal routing.
# Dynamic host port edge discovers via Nomad service registration.
# No static port to avoid collisions with edge (which owns 80/443).
#
# Not the runtime yet: docker-compose.yml is still the factory's live stack
# until cutover. This file exists so CI can validate it and S5.2 can wire
@ -27,11 +27,10 @@ job "staging" {
# No Vault integration needed no secrets required (static file server)
# Internal service no external port. Edge proxy routes internally.
# Internal service dynamic host port. Edge discovers via Nomad service.
network {
port "http" {
static = 80
to = 80
to = 80
}
}