Add detailed debugging steps for rsync permission issue

- Test directory access and permissions
- Check user identity and current directory
- Create target directory if not exists
- Add verbose SSH logging (-vvv) to rsync
- Troubleshoot permission denied error step by step

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.github/workflows/deploy.yml

@@ -31,9 +31,19 @@ jobs:
           ssh -o StrictHostKeyChecking=no -p ${{ secrets.NAS_PORT }} \
             ${{ secrets.NAS_USER }}@${{ secrets.NAS_HOST }} echo "SSH connection successful"
 
-      - name: Rsync to NAS
+      - name: Test directory access
         run: |
-          rsync -avz -e "ssh -p ${{ secrets.NAS_PORT }}" ./ \
+          ssh -p ${{ secrets.NAS_PORT }} admin@${{ secrets.NAS_HOST }} \
+            "ls -la /volume1/homes/admin/ && whoami && pwd"
+
+      - name: Create target directory if not exists
+        run: |
+          ssh -p ${{ secrets.NAS_PORT }} admin@${{ secrets.NAS_HOST }} \
+            "mkdir -p /volume1/homes/admin/nginx-infra && ls -la /volume1/homes/admin/nginx-infra"
+
+      - name: Rsync to NAS (with verbose SSH)
+        run: |
+          rsync -avz -e "ssh -vvv -p ${{ secrets.NAS_PORT }}" ./ \
             admin@${{ secrets.NAS_HOST }}:/volume1/homes/admin/nginx-infra/
 
       - name: Remote docker-compose up