Update deployment workflow for blue-green strategy: Renamed workflow to 'Deploy yourpart (blue-green)' and refactored SSH connection steps to utilize environment variables for host, port, and user. Changed deployment script to align with blue-green deployment practices, enhancing clarity and maintainability.

.gitea/workflows/deploy-daemon.yml

@@ -1,4 +1,4 @@
-name: Deploy daemon
+name: Deploy yourpart (blue-green)
 
 on:
   push:
@@ -6,16 +6,21 @@ on:
       - main
 
 jobs:
-  deploy-daemon:
+  deploy:
     runs-on: ubuntu-latest
 
+    env:
+      HOST: ${{ vars.PROD_HOST }}
+      PORT: ${{ vars.PROD_PORT }}
+      USER: ${{ vars.PROD_USER }}
+
     steps:
       - name: Prepare SSH
         run: |
           mkdir -p ~/.ssh
           printf "%s" "${{ secrets.PROD_SSH_KEY }}" > ~/.ssh/id_ed25519
           chmod 600 ~/.ssh/id_ed25519
-          ssh-keyscan -p "${{ secrets.PROD_PORT }}" "${{ secrets.PROD_HOST }}" >> ~/.ssh/known_hosts
+          ssh-keyscan -p "$PORT" "$HOST" >> ~/.ssh/known_hosts
 
       - name: Test SSH connection
         run: |
@@ -23,16 +28,16 @@ jobs:
             -o StrictHostKeyChecking=no \
             -o BatchMode=yes \
             -o ConnectTimeout=10 \
-            -p "${{ secrets.PROD_PORT }}" \
-            "${{ secrets.PROD_USER }}@${{ secrets.PROD_HOST }}" \
+            -p "$PORT" \
+            "$USER@$HOST" \
             "echo SSH OK"
 
-      - name: Run daemon deployment script
+      - name: Run blue-green deployment
         run: |
           ssh -i ~/.ssh/id_ed25519 \
             -o StrictHostKeyChecking=no \
             -o BatchMode=yes \
             -o ConnectTimeout=10 \
-            -p "${{ secrets.PROD_PORT }}" \
-            "${{ secrets.PROD_USER }}@${{ secrets.PROD_HOST }}" \
-            "/home/tsschulz/deploy-yourpart-daemon-bluegreen.sh"
+            -p "$PORT" \
+            "$USER@$HOST" \
+            "/home/tsschulz/deploy-yourpart-bluegreen.sh"