From 72456aa7a0c2e78959e6e7fe98528c5257d66e3c Mon Sep 17 00:00:00 2001
From: denshooter <dennis@konkol.net>
Date: Sat, 13 Sep 2025 00:35:02 +0200
Subject: [PATCH] Fix Docker Compose command syntax

- Replace deprecated 'docker-compose' with modern 'docker compose'
- Update all workflow files to use new syntax
- Update documentation with correct commands
- Fixes 'command not found' error in CI/CD pipeline
- Compatible with Docker Compose V2 and newer versions
---
 .gitea/workflows/ci-cd.yml |  4 ++--
 DEPLOYMENT.md              | 40 +++++++++++++++++++-------------------
 2 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/.gitea/workflows/ci-cd.yml b/.gitea/workflows/ci-cd.yml
index 6bcda2e..c08734d 100644
--- a/.gitea/workflows/ci-cd.yml
+++ b/.gitea/workflows/ci-cd.yml
@@ -81,7 +81,7 @@ jobs:
 
       - name: Stop existing services
         run: |
-          docker-compose down || true
+          docker compose down || true
 
       - name: Verify secrets and variables before deployment
         run: |
@@ -119,7 +119,7 @@ jobs:
 
       - name: Start services with Docker Compose
         run: |
-          docker-compose up -d
+          docker compose up -d
         env:
           NODE_ENV: ${{ vars.NODE_ENV }}
           LOG_LEVEL: ${{ vars.LOG_LEVEL }}
diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md
index aec7786..f6e1a67 100644
--- a/DEPLOYMENT.md
+++ b/DEPLOYMENT.md
@@ -48,13 +48,13 @@ Configure these secrets in your Gitea repository (Settings → Secrets):
 
 ```bash
 # Start all services
-docker-compose up -d
+docker compose up -d
 
 # View logs
-docker-compose logs -f portfolio
+docker compose logs -f portfolio
 
 # Stop services
-docker-compose down
+docker compose down
 ```
 
 ### 2. CI/CD Pipeline (Automatic)
@@ -76,13 +76,13 @@ The CI/CD pipeline runs automatically on:
 
 ```bash
 # Build and start services
-docker-compose up -d --build
+docker compose up -d --build
 
 # Check service status
-docker-compose ps
+docker compose ps
 
 # View logs
-docker-compose logs -f
+docker compose logs -f
 ```
 
 ## Service Configuration
@@ -116,31 +116,31 @@ docker-compose logs -f
 2. **Container won't start**:
    ```bash
    # Check logs
-   docker-compose logs portfolio
+   docker compose logs portfolio
    
    # Check service status
-   docker-compose ps
+   docker compose ps
    
    # Restart services
-   docker-compose restart
+   docker compose restart
    ```
 
 3. **Database connection issues**:
    ```bash
    # Check PostgreSQL status
-   docker-compose exec postgres pg_isready -U portfolio_user -d portfolio_db
+   docker compose exec postgres pg_isready -U portfolio_user -d portfolio_db
    
    # Check database logs
-   docker-compose logs postgres
+   docker compose logs postgres
    ```
 
 4. **Redis connection issues**:
    ```bash
    # Test Redis connection
-   docker-compose exec redis redis-cli ping
+   docker compose exec redis redis-cli ping
    
    # Check Redis logs
-   docker-compose logs redis
+   docker compose logs redis
    ```
 
 ### Debug Commands
@@ -153,7 +153,7 @@ docker exec portfolio-app env | grep -E "(DATABASE_URL|REDIS_URL|NEXT_PUBLIC_BAS
 curl -f http://localhost:3000/api/health
 
 # View all service logs
-docker-compose logs --tail=50
+docker compose logs --tail=50
 
 # Check resource usage
 docker stats
@@ -169,12 +169,12 @@ docker stats
 ### Logs
 ```bash
 # Follow all logs
-docker-compose logs -f
+docker compose logs -f
 
 # Follow specific service logs
-docker-compose logs -f portfolio
-docker-compose logs -f postgres
-docker-compose logs -f redis
+docker compose logs -f portfolio
+docker compose logs -f postgres
+docker compose logs -f redis
 ```
 
 ## Security
@@ -195,10 +195,10 @@ docker-compose logs -f redis
 ### Database Backup
 ```bash
 # Create backup
-docker-compose exec postgres pg_dump -U portfolio_user portfolio_db > backup.sql
+docker compose exec postgres pg_dump -U portfolio_user portfolio_db > backup.sql
 
 # Restore backup
-docker-compose exec -T postgres psql -U portfolio_user portfolio_db < backup.sql
+docker compose exec -T postgres psql -U portfolio_user portfolio_db < backup.sql
 ```
 
 ### Volume Backup