Commit graph

3 commits

Author SHA1 Message Date
Vadym Samoilenko
9afda2069e Fix port binding: replace !reset with !override in prod compose overlay
In Compose v5, !reset resets a key to its default (empty) and ignores
the provided values. !override replaces the existing list entirely,
which is the correct behaviour for restricting ports to 127.0.0.1.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-19 21:12:15 +00:00
Vadym Samoilenko
d10759b4de Fix port conflict: use !reset tag to replace base ports, not append
Docker Compose merges port lists from multiple -f files by concatenation.
Without !reset, both 0.0.0.0:8000:8000 (base) and 127.0.0.1:8000:8000
(prod override) are applied simultaneously, causing "port already allocated".
!reset clears the list before applying prod-specific bindings (requires
Docker Compose v2.24+, available in current docker-compose-plugin via apt).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-19 20:33:37 +00:00
Vadym Samoilenko
7c8b8cd369 Add production deploy script and Apache/Docker config
- deploy.sh: idempotent 12-step deploy for Ubuntu (prereqs, port
  conflict check, basePath patch, build, migrate, Apache + UFW setup)
- docker-compose.prod.yml: prod overrides (127.0.0.1 bindings, no nginx)
- apache/deckforge.conf: reverse proxy template with SSE support

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-19 19:15:19 +00:00