Three related fixes from PR #493 deploy incident (deploy/1156 failed at
bootstrap; tradein-backend USER MAPPING never created):
1. deploy-tradein.yml — restart tradein-backend AFTER SQL migrations apply.
Root cause: `compose up -d` runs at line 157 before migrations at line 163,
so tradein-backend lifespan hook (ensure_fdw_user_mapping) tries to
CREATE USER MAPPING against FOREIGN SERVER gendesign_remote that doesn't
exist yet (created by 060_postgres_fdw_extension.sql later). Hook fails
permanently with `psycopg.errors.UndefinedObject: server "gendesign_remote"
does not exist`; never retried. Restart after migrations triggers retry.
2. deploy.yml — extract inline psql DO block into ops/db-bootstrap/
set_tradein_fdw_password.sql, run via `psql -v pw=$ENV -f <file>`.
Original block used multi-line backslash continuations inside double-quoted
bash string with $$-dollar-quoting + psql var substitution — fragile
escaping likely caused deploy/1156 failure between migration apply (09:01:03)
and compose up -d. Clean .sql file with `-v pw=` substitution is safe and
psql-native.
3. deploy.yml — verify postgres in gendesign_shared after `compose up -d`,
force-recreate if not. Compose sometimes skips recreate on network membership
change (PR #493 introduced `networks: shared (alias gendesign-postgres)` to
postgres service). Without postgres in shared, tradein-postgres can't resolve
DNS `gendesign-postgres` -> FDW queries fail with "could not translate host
name". Manual fix on prod: `docker network connect --alias gendesign-postgres
gendesign_shared gendesign-postgres-1`.
No code changes — only deploy workflow and one new SQL file.
502 fix: Next.js standalone server.js биндился на HOSTNAME=<container-id>
вместо 0.0.0.0 → Caddy не мог достучаться до tradein-frontend:3000.
Теперь HOSTNAME=0.0.0.0 и в Dockerfile (runner ENV), и в compose.
API routing fix: фронт собирался без NEXT_PUBLIC_API_BASE_URL, fetch шёл
на same-origin /api/* (главный gendesign-backend) вместо /trade-in/api/*.
Добавлен build-arg в Dockerfile + workflow.
