Make the Docker build and compose smoke test pass

Fixes found while validating `docker compose up`:
- Copy .editorconfig into the build context and stop ignoring it — the in-container
  publish needs its analyzer suppressions (CA1848/CA1873) or warnings-as-errors fails.
- npm ci uses npmjs.org (the Nexus npm proxy 404s on some packages; npmjs.org is
  reachable from this machine); base images + NuGet still go through the mirror.
- Parameterize the Postgres/web host ports (defaults 5432/8080) so the stack doesn't
  clash with other local Postgres instances.

Verified: image builds; `compose up` brings up Postgres (healthy) + web + worker on one
image (RUN_MODE) — /health 200, /api/orgboard/ping ok, the SPA serves at /, and the
worker logs "DB health: Healthy" heartbeats.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
soroush.asadi
2026-06-09 07:07:07 +03:30
parent 36fe158b43
commit 265861b89b
3 changed files with 7 additions and 5 deletions
+1 -2
View File
@@ -11,11 +11,10 @@ client/node_modules/
client/dist/
client/.vite/
# VCS / docs / local
# VCS / docs / local (.editorconfig is NOT ignored — the in-container build needs its analyzer rules)
.git/
.gitignore
.gitattributes
*.md
docs/
.editorconfig
**/appsettings.*.local.json