soroush.asadi
1a6a0dc495
CI/CD / CI · API (dotnet build + test) (push) Successful in 43s
CI/CD / CI · Admin API (dotnet build) (push) Successful in 31s
CI/CD / CI · Dashboard (tsc) (push) Successful in 1m4s
CI/CD / CI · Admin Web (tsc) (push) Successful in 35s
CI/CD / CI · Website (tsc) (push) Successful in 44s
CI/CD / CI · Koja (tsc) (push) Successful in 49s
CI/CD / Deploy · all services (push) Failing after 10s
docker compose up without --no-recreate tries to recreate postgres/redis when it detects a config change or finds a stopped container, which causes "container name already in use" when the container is still running. Fix: infrastructure (postgres, redis) uses --no-recreate so a healthy container is never touched. App services (api, web, website, koja, admin-api, admin-web) use --force-recreate so freshly-built images are always applied. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>