User reported persistent 502 with upstream "frontend:3000" after the previous fix that changed the upstream to "frontend:80". Symptom is a stale conf still being served by the nginx container - the host volume mount was keeping an old file in play (cached image, missing git pull, or the conf simply not being re-read). Make this class of bug impossible: ship the conf inside the nginx service's image. A fresh build now guarantees the conf in the container matches the conf in the repo. - nginx/Dockerfile added (FROM nginx:alpine + COPY nginx.conf) - docker-compose nginx service: image -> build ./nginx; remove the conf bind mount entirely. Deploy: git pull && docker compose build nginx frontend && docker compose up -d --force-recreate
48 lines
852 B
YAML
48 lines
852 B
YAML
services:
|
|
proxy:
|
|
build: ./proxy
|
|
container_name: mc-filter-proxy
|
|
ports:
|
|
- "25565:25565"
|
|
volumes:
|
|
- ./data:/data
|
|
restart: unless-stopped
|
|
networks:
|
|
- mc-filter
|
|
|
|
api:
|
|
build: ./api
|
|
container_name: mc-filter-api
|
|
expose:
|
|
- "8000"
|
|
volumes:
|
|
- ./data:/data
|
|
restart: unless-stopped
|
|
networks:
|
|
- mc-filter
|
|
|
|
frontend:
|
|
build: ./frontend
|
|
container_name: mc-filter-frontend
|
|
expose:
|
|
- "80"
|
|
restart: unless-stopped
|
|
networks:
|
|
- mc-filter
|
|
|
|
nginx:
|
|
build: ./nginx
|
|
container_name: mc-filter-nginx
|
|
ports:
|
|
- "8080:80" # 대시보드 접근 포트 (외부 포트포워딩 금지 권장)
|
|
depends_on:
|
|
- api
|
|
- frontend
|
|
restart: unless-stopped
|
|
networks:
|
|
- mc-filter
|
|
|
|
networks:
|
|
mc-filter:
|
|
driver: bridge
|