diff --git a/.env.production b/.env.production new file mode 100644 index 0000000..fdaeee0 --- /dev/null +++ b/.env.production @@ -0,0 +1,15 @@ +# Database credentials (must match existing PostgreSQL volume) +DB_USER=bbdf554 +DB_PASSWORD=Idk@2026lolhappyha232 +DB_DATABASE=directus + +# Admin credentials +ADMIN_EMAIL=somescreenname@gmail.com +ADMIN_PASSWORD=Idk@2026lolhappyha232 + +# Directus keys +KEY=9i2t1bMAIITWCZ+WrzUEk4EuNmIu3kfyB9Peysk7f/jnUZ7hzQ5HoNC8yOT5vi/rwTmDWX3a1+4j2llgAE2VvA== +SECRET=Mr4YSrOAfwToxCDFOPwUa8qtxd7BXOvmqXalk3ReikpfcIwf08Kp+hlNjGcr1NtcLIcIZoraaULnMefD5IukGA== + +# Optional +DIRECTUS_ADMIN_TOKEN= diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md new file mode 100644 index 0000000..3295c80 --- /dev/null +++ b/TROUBLESHOOTING.md @@ -0,0 +1,35 @@ +# Database Credentials Issue - Troubleshooting + +## Problem +Directus is trying to connect with user `sparkuser` but the database has user `bbdf554`. + +## Root Cause +Coolify might have environment variables that override the docker-compose.yaml values. + +## Solution Options + +### Option 1: Check Coolify Environment Variables +In Coolify UI → Application → Environment Variables: +- Look for `DB_USER` variable +- If it says `sparkuser`, delete it or change to `bbdf554` + +### Option 2: Add .env file to override +Create a `.env` file in the repo with: +``` +DB_USER=bbdf554 +DB_PASSWORD=Idk@2026lolhappyha232 +``` + +### Option 3: Hardcode in docker-compose (already done) +The docker-compose.yaml already has hardcoded values, but Coolify's `env_file: .env` might be overriding them. + +## Current Status +- PostgreSQL: ✅ Running with user `bbdf554` +- Redis: ✅ Running +- Frontend: ✅ Running +- Directus: ❌ Can't connect (wrong username) + +## Next Steps +1. Check if Coolify has environment variable overrides +2. Remove any `DB_USER=sparkuser` variables +3. Redeploy diff --git a/docker-compose.yaml b/docker-compose.yaml index f8ac428..33002ef 100644 --- a/docker-compose.yaml +++ b/docker-compose.yaml @@ -11,7 +11,7 @@ services: POSTGRES_PASSWORD: Idk@2026lolhappyha232 POSTGRES_DB: directus healthcheck: - test: ["CMD-SHELL", "pg_isready -h 127.0.0.1"] + test: [ "CMD-SHELL", "pg_isready -h 127.0.0.1" ] interval: 5s timeout: 5s retries: 10 @@ -23,7 +23,7 @@ services: volumes: - 'redis-data:/data' healthcheck: - test: ["CMD", "redis-cli", "ping"] + test: [ "CMD", "redis-cli", "ping" ] interval: 5s timeout: 5s retries: 5 @@ -46,20 +46,20 @@ services: # Match existing database credentials DB_USER: bbdf554 DB_PASSWORD: Idk@2026lolhappyha232 - + MAX_PAYLOAD_SIZE: '500mb' RATE_LIMITER_ENABLED: 'false' CORS_ORIGIN: 'https://launch.jumpstartscaling.com,http://localhost:4321' CORS_ENABLED: 'true' PUBLIC_URL: 'https://spark.jumpstartscaling.com' - + depends_on: postgresql: condition: service_healthy redis: condition: service_healthy healthcheck: - test: ["CMD", "wget", "--spider", "--no-verbose", "http://127.0.0.1:8055/server/health"] + test: [ "CMD", "wget", "--spider", "--no-verbose", "http://127.0.0.1:8055/server/health" ] interval: 10s timeout: 5s retries: 5 @@ -92,3 +92,6 @@ volumes: redis-data: directus-uploads: directus-extensions: + + # NOTE: No env_file specified - all credentials are hardcoded above + # This prevents Coolify from loading external .env files that might override values