cesnimda/Inboxintel
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Fix staging auto-deploy: env write + port isolation #3

Merged
cesnimda merged 1 commits from fix/staging-parity into develop 2026-07-01 12:50:12 +02:00
Conversation 0 Commits 1 Files Changed 2
+16 -15

1 Commits

Author SHA1 Message Date
cesnimda 3f8b5c6ea4 fix(staging): robust env write + stop double-binding prod ports
CI / backend (pull_request) Successful in 1m2s
Details
CI / frontend (pull_request) Successful in 21s
Details
Security / secrets (pull_request) Successful in 6s
Details
Security / dependencies (pull_request) Successful in 1m4s
Details 
Two fixes to the auto-deploy path found on the first host-mode run:
- Write deploy/.env.staging line-by-line instead of a here-string, so the step
  can't be broken by how act_runner indents/wraps the PowerShell script (the
  here-string terminator must be col 0; the runner's wrapping broke it, leaving
  POSTGRES_PASSWORD blank so postgres/api failed while frontend came up).
- Tag the staging 'ports' lists with !override so the overlay REPLACES the base
  ports instead of merging — staging no longer also binds prod's 8080/8081.
Verified locally: compose config shows only 18080/18081/15432.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-07-01 12:44:14 +02:00