Refactor CI workflow and update documentation for Azure VM deployment; remove emoji from step names, enhance clarity, and add detailed deployment instructions.

Author: YosefKahlon

.github/workflows/ci_week7.yml

@@ -10,18 +10,18 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - name: 📥 Checkout code
+      - name: Checkout code
         uses: actions/checkout@v4
 
-      - name: 🔧 Build Docker containers
+      - name: Build Docker containers
         run: docker compose build
         working-directory: week7
 
-      - name: 🚀 Start containers
+      - name: Start containers
         run: docker compose up -d
         working-directory: week7
 
-      - name: 💤 Wait for DB healthcheck
+      - name: Wait for DB healthcheck
         run: |
           timeout=30
           for i in $(seq 1 $timeout); do
@@ -32,7 +32,7 @@ jobs:
           done
         working-directory: week7
 
-      - name: 💤 Wait for backend to become healthy
+      - name: Wait for backend to become healthy
         run: |
           timeout=30
           for i in $(seq 1 $timeout); do
@@ -43,25 +43,55 @@ jobs:
           done
         working-directory: week7
 
-      - name: 🧪 Test API endpoints
+      - name: Test API endpoints
         run: |
           curl --fail http://localhost:3000/health
           curl --fail http://localhost:3000/api/users
         working-directory: week7
 
-      - name: 📜 Capture logs on failure
+      - name: Capture logs on failure
         if: failure()
         run: docker compose logs > full_logs.txt
         working-directory: week7
 
-      - name: 📤 Upload logs
+      - name: Upload logs
         if: always()
         uses: actions/upload-artifact@v4
         with:
           name: docker-compose-logs
           path: week7/full_logs.txt
 
-      - name: 🧹 Shut down containers
+      - name: Shut down containers
         if: always()
         run: docker compose down --volumes
         working-directory: week7
+
+        
+  deploy:
+    needs: e2e
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up SSH key
+        run: |
+          mkdir -p ~/.ssh
+          echo "${{ secrets.AZURE_VM_KEY }}" > ~/.ssh/myDockerVM_key.pem
+          chmod 600 ~/.ssh/myDockerVM_key.pem
+
+      - name: Copy files to Azure VM (excluding frontend)
+        run: |
+          rsync -av --exclude=frontend -e "ssh -i ~/.ssh/myDockerVM_key.pem -o StrictHostKeyChecking=no" week7/ ${{ secrets.AZURE_VM_USER }}@${{ secrets.AZURE_VM_HOST }}:~/week7/
+
+      - name: Deploy with Docker Compose on Azure VM
+        run: |
+          ssh -i ~/.ssh/myDockerVM_key.pem -o StrictHostKeyChecking=no ${{ secrets.AZURE_VM_USER }}@${{ secrets.AZURE_VM_HOST }} "
+            cd ~/week7 && docker-compose up --build -d
+          "
+
+      - name: Check service health on Azure VM
+        run: |
+          ssh -i ~/.ssh/myDockerVM_key.pem -o StrictHostKeyChecking=no ${{ secrets.AZURE_VM_USER }}@${{ secrets.AZURE_VM_HOST }} "
+            curl -f http://localhost:3000/health

week7/Docker Compose & Azure+VM.md

@@ -73,6 +73,73 @@ In this example we **Defined a `docker-compose.yml` file** with a basic multi-se
    docker-compose logs backend
    ```
 
+ # Azure VM Setup and Manual Deployment
 
+1. **Created an Azure Virtual Machine (VM):**
+   - Used the Azure Portal or Azure CLI to create a Linux VM (Ubuntu) with a public IP and an admin username (`azureuser`).
+   - Downloaded the private SSH key (`myDockerVM_key.pem`) for secure access.
+   - Store the key in ~/.ssh/ folder.
 
+2. **Configured SSH Access:**
+   - Set permissions on the key file using `chmod 600 ~/.ssh/myDockerVM_key.pem`.
+   - Connected to the VM using:
+     ```bash
+     ssh -i ~/.ssh/myDockerVM_key.pem azureuser@<vm-public-ip>
+     ```
+
+3. **Installed Docker and Docker Compose on the VM:**
+   - Updated the package list and installed Docker:
+     ```bash
+     sudo apt-get update
+     sudo apt-get install -y docker.io
+     sudo systemctl enable --now docker
+     sudo usermod -aG docker $USER
+     ```
+   - Installed Docker Compose:
+     ```bash
+     sudo apt-get install -y docker-compose
+     ```
+   - Logged out and back in (or used `newgrp docker`) to apply Docker group permissions.
+
+4. **Deployed the Application:**
+   - Copied the application files (excluding the `frontend` folder) from the local machine to the VM using `rsync`:
+     ```bash
+     rsync -av --exclude=frontend -e "ssh -i ~/.ssh/myDockerVM_key.pem" /home/yosef/Documents/github/DevOps-Linux/DevOps-Linux/week7/ azureuser@<vm-public-ip>:~/week7/
+     ```
+   - Navigated to the app directory on the VM:
+     ```bash
+     cd ~/week7
+     ```
+
+5. **Started the Application with Docker Compose:**
+   - Built and started the containers:
+     ```bash
+     docker-compose up --build -d
+     ```
+   - Verified that the containers are running:
+     ```bash
+     docker-compose ps
+     ```
+
+6. **Exposed the Application on a Public Port:**
+   - Ensured port 3000 was open in Azure Network Security Group settings.
+   - Accessed the running application from a browser or with `curl`:
+     ```
+     http://<vm-public-ip>:3000
+     ```
+
+7. **Tested the API:**
+   - Used `curl` to test the health endpoint and add users:
+     ```bash
+     curl http://localhost:3000/health
+     curl -X POST http://localhost:3000/api/users -H "Content-Type: application/json" -d '{"name": "Alice", "email": "alice@example.com"}'
+     ```
+
+**Result:**  
+The application is now running on the Azure VM, accessible from the public IP on port 3000, and can be managed using Docker Compose.
+
+
+# Deploy to Azure VM via CI/CD 
 
+insted of manuly we can use automte tool like github action 
+