chpark/distribution_erp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: deploy 단계를 build → down → up 패턴으로 (컨테이너 이름 충돌 방지)
Deploy momo-erp / deploy (push) Successful in 52s
Details

Browse Source 
5cbc324 배포 시 --force-recreate 가 이름 충돌(Conflict, 65adeb31db46_momo-erp)을
일으켜 컨테이너 swap 실패. 명시적으로 down --remove-orphans 후 up 으로 분리.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
chpark
2026-05-08 13:45:48 +09:00
parent 5cbc324627
commit ffada52fd4
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+4 -2
View File
@@ -62,8 +62,10 @@ jobs:
DEPLOY_WEBHOOK_TOKEN=momo-deploy-2026-secure DEPLOY_WEBHOOK_TOKEN=momo-deploy-2026-secure
ENVEOF ENVEOF
# --force-recreate: docker compose 가 변화 감지 못해 컨테이너 swap 안 하는 케이스 방지 # 빌드는 먼저, 그 다음 down + up 으로 swap (--force-recreate 가 가끔 이름 충돌 일으킴)
docker compose -f docker-compose.prod.yml up -d --build --force-recreate momo-erp docker compose -f docker-compose.prod.yml build momo-erp
docker compose -f docker-compose.prod.yml down --remove-orphans
docker compose -f docker-compose.prod.yml up -d momo-erp
# 마이그레이션 (idempotent) — 컨테이너 안에 db/migrations + scripts/migrate-momo.mjs 가 # 마이그레이션 (idempotent) — 컨테이너 안에 db/migrations + scripts/migrate-momo.mjs 가
# standalone 번들에 포함되어 있어야 동작 (next.config.ts outputFileTracingIncludes). # standalone 번들에 포함되어 있어야 동작 (next.config.ts outputFileTracingIncludes).