fix: Change exposed ports to avoid conflicts
Some checks failed
build-and-deploy / filter (push) Successful in 2s
build-and-deploy / build (push) Successful in 6s
build-and-deploy / deploy (push) Failing after 1m44s

- Server: 2567 → 3067 (host:container)
- Client: 3000 → 3010 (host:container)
- Admin: 3001 → 3011 (host:container)
- Internal container ports remain the same
This commit is contained in:
2025-07-05 15:17:18 -06:00
parent 78faae2ce7
commit 58ca3d1e73

View File

@@ -6,7 +6,7 @@ services:
image: gitea.interno.com/nucleo000/snatchgame-server:latest image: gitea.interno.com/nucleo000/snatchgame-server:latest
container_name: snatchgame-server container_name: snatchgame-server
ports: ports:
- "2567:2567" - "3067:2567"
environment: environment:
- NODE_ENV=production - NODE_ENV=production
- PORT=2567 - PORT=2567
@@ -25,7 +25,7 @@ services:
image: gitea.interno.com/nucleo000/snatchgame-client:latest image: gitea.interno.com/nucleo000/snatchgame-client:latest
container_name: snatchgame-client container_name: snatchgame-client
ports: ports:
- "3000:3000" - "3010:3000"
environment: environment:
- NODE_ENV=production - NODE_ENV=production
- PORT=3000 - PORT=3000
@@ -47,7 +47,7 @@ services:
image: gitea.interno.com/nucleo000/snatchgame-admin:latest image: gitea.interno.com/nucleo000/snatchgame-admin:latest
container_name: snatchgame-admin container_name: snatchgame-admin
ports: ports:
- "3001:3001" - "3011:3001"
environment: environment:
- NODE_ENV=production - NODE_ENV=production
- PORT=3001 - PORT=3001