Joakim Mörling dfcc8e37c6 fix: isolate prod deploy from dev env port conflict ... The production deploy failed because port 3000 was already bound by the dev frontend container (bilhej-frontend). The prod frontend doesn't need a host port at all — nginx talks to it via the external 'web' network. Changes: - Remove host port binding (3000:80) from prod frontend - Remove unused 'certs' volume from prod compose - Use --project-name bilhej-prod in deploy workflow to isolate prod containers/networks from dev and e2e environments - Add 'docker compose down' before 'up' for clean deploys - Update health check network names to bilhej-prod_default		2026-05-20 12:45:08 +02:00
..
ci.yml	ci: fix coverage summary table — remove Status column and trailing empty cell	2026-05-19 20:40:26 +02:00
deploy.yml	fix: isolate prod deploy from dev env port conflict	2026-05-20 12:45:08 +02:00