Remmer/stiftung-management-system
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix deployment pipeline - use main compose.yml instead of deploy-production

Browse Source 
- Remove reference to deploy-production/docker-compose.prod.yml (now archived)
- Use compose.yml directly as the production configuration
- This should fix the deployment script and enable proper image updates
This commit is contained in:
Stiftung Development
2025-09-17 19:54:23 +02:00
parent ebb9a1f887
commit cbde96698b
1 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.github/workflows/ci-cd.yml vendored
View File

@@ -211,13 +211,9 @@ jobs:
# Pull latest code changes (.env is in .gitignore so won't be touched) # Pull latest code changes (.env is in .gitignore so won't be touched)
git pull https://$DEPLOY_TOKEN@github.com/remmerinio/stiftung-management-system.git main git pull https://$DEPLOY_TOKEN@github.com/remmerinio/stiftung-management-system.git main
# Backup current compose.yml # The main compose.yml is already the correct production configuration
if [ -f compose.yml ]; then # No need to copy from deploy-production since we use compose.yml directly
cp compose.yml compose.yml.backup echo "Using main compose.yml for production deployment"
fi
# Copy production docker compose file to the active compose.yml
cp deploy-production/docker-compose.prod.yml compose.yml
# Try to login to GitHub Container Registry and pull images # Try to login to GitHub Container Registry and pull images
echo "Attempting to pull images from GitHub Container Registry..." echo "Attempting to pull images from GitHub Container Registry..."