From cbde96698b3a011122c71023c856a4337d3bd1e5 Mon Sep 17 00:00:00 2001 From: Stiftung Development Date: Wed, 17 Sep 2025 19:54:23 +0200 Subject: [PATCH] Fix deployment pipeline - use main compose.yml instead of deploy-production - 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 --- .github/workflows/ci-cd.yml | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/.github/workflows/ci-cd.yml b/.github/workflows/ci-cd.yml index c24fb71..1422d80 100644 --- a/.github/workflows/ci-cd.yml +++ b/.github/workflows/ci-cd.yml @@ -211,13 +211,9 @@ jobs: # 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 - # Backup current compose.yml - if [ -f compose.yml ]; then - cp compose.yml compose.yml.backup - fi - - # Copy production docker compose file to the active compose.yml - cp deploy-production/docker-compose.prod.yml compose.yml + # The main compose.yml is already the correct production configuration + # No need to copy from deploy-production since we use compose.yml directly + echo "Using main compose.yml for production deployment" # Try to login to GitHub Container Registry and pull images echo "Attempting to pull images from GitHub Container Registry..."