weefnn/full-stack-fastapi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: force compose to use .env.production in deploy workflow
Some checks failed
Deploy to Production / deploy (push) Failing after 5s
Details

Browse Source
This commit is contained in:
codex
2026-03-11 17:15:02 +08:00
parent 6defbf92e0
commit e860fd0607
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.gitea/workflows/deploy.yml
View File

@@ -44,13 +44,13 @@ jobs:
ENVEOF
- name: Build Docker images
run: docker compose -f compose.prod.yml build
run: docker compose --env-file .env.production -f compose.prod.yml build
- name: Stop existing services
run: docker compose -f compose.prod.yml down --remove-orphans || true
run: docker compose --env-file .env.production -f compose.prod.yml down --remove-orphans || true
- name: Start services
run: docker compose -f compose.prod.yml up -d
run: docker compose --env-file .env.production -f compose.prod.yml up -d
- name: Wait for backend health check
run: |
@@ -64,7 +64,7 @@ jobs:
sleep 10
done
echo "❌ Backend health check failed after 300s"
docker compose -f compose.prod.yml logs backend
docker compose --env-file .env.production -f compose.prod.yml logs backend
exit 1
- name: Verify frontend
@@ -73,7 +73,7 @@ jobs:
echo "✅ Frontend is accessible!"
else
echo "❌ Frontend is not accessible"
docker compose -f compose.prod.yml logs frontend
docker compose --env-file .env.production -f compose.prod.yml logs frontend
exit 1
fi