disinto-admin/disinto
1
0
Fork 0
Code Issues 22 Pull requests 1 Projects Releases Packages Wiki Activity Actions

fix: [nomad-step-5] edge caddy task fails to clone Forgejo from 127.0.0.1:3000 under bridge network (#1034)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/push/nomad-validate Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
ci/woodpecker/pr/nomad-validate Pipeline was successful
Details
ci/woodpecker/pr/secret-scan Pipeline was successful
Details

Browse source
This commit is contained in:
dev-qwen2 2026-04-19 09:45:02 +00:00
parent 2648c401f4
commit ada27759de
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
nomad/jobs/edge.hcl
View file

@ -225,6 +225,21 @@ EOT
read_only = false read_only = false
} }
# ── Forge URL via Nomad service discovery (issue #1034) ──────────
# Resolves forgejo service address/port dynamically for bridge network
# compatibility. Template-scoped to dispatcher task (Nomad doesn't
# propagate templates across tasks).
template {
destination = "local/forge.env"
env = true
change_mode = "restart"
data = <<EOT
{{ range service "forgejo" -}}
FORGE_URL=http://{{ .Address }}:{{ .Port }}
{{- end }}
EOT
}
# ── Vault-templated secrets (S5.1, issue #988) ────────────────────── # ── Vault-templated secrets (S5.1, issue #988) ──────────────────────
# Renders FORGE_TOKEN from Vault KV v2 for ops repo access. # Renders FORGE_TOKEN from Vault KV v2 for ops repo access.
template { template {