# ModComms Deployment Configuration
# Copy this file to .env.deploy and update with your server values
#
# For running prod and dev on the same server, clone the repo twice:
#   /opt/modcomms-prod/  - production (main branch)
#   /opt/modcomms-dev/   - development (develop branch)
# Then configure each .env.deploy with different values below.

# Docker project name (creates unique container names)
# Examples: modcomms-prod, modcomms-dev
COMPOSE_PROJECT_NAME=modcomms-prod

# Backend port (must be unique per instance)
# Examples: 8000 for prod, 8001 for dev
BACKEND_PORT=8000

# PostgreSQL port (must be unique per instance)
# Examples: 5432 for prod, 5433 for dev
POSTGRES_PORT=5432

# PostgreSQL credentials (change in production!)
POSTGRES_USER=modcomms
POSTGRES_PASSWORD=change_this_in_production
POSTGRES_DB=modcomms

# Frontend deployment directory (Apache document root)
# Examples: /var/www/modcomms-prod, /var/www/modcomms-dev
FRONTEND_DEPLOY_DIR=/var/www/html/modcomms

# CORS origins (should match your frontend domain)
# Multiple origins can be comma-separated
CORS_ORIGINS=https://your-domain.com

# NOTE: Frontend environment variables (VITE_*) are NOT configured here.
# Create frontend/.env.local manually with:
#   VITE_BACKEND_WS_URL=wss://your-domain.com/ws/analyze
#   VITE_BACKEND_URL=https://your-domain.com
#   VITE_AZURE_CLIENT_ID=your_azure_client_id
#   VITE_AZURE_TENANT_ID=your_azure_tenant_id
#   VITE_AZURE_REDIRECT_URI=https://your-domain.com