27113a625a
- Add COMPOSE_PROJECT_NAME for unique container names - Add BACKEND_PORT for configurable port mapping - Update deploy.sh to export variables for docker compose - Update health checks to use configured port Allows running prod and dev instances simultaneously by cloning the repo twice with different .env.deploy configurations. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
28 lines
1 KiB
Text
28 lines
1 KiB
Text
# 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
|
|
|
|
# Frontend deployment directory (Apache document root)
|
|
# Examples: /var/www/modcomms-prod, /var/www/modcomms-dev
|
|
FRONTEND_DEPLOY_DIR=/var/www/html/modcomms
|
|
|
|
# Backend URLs (used during frontend build)
|
|
# These should match your domain/vhost configuration
|
|
VITE_BACKEND_WS_URL=wss://your-domain.com/ws/analyze
|
|
VITE_BACKEND_URL=https://your-domain.com
|
|
|
|
# CORS origins (should match your frontend domain)
|
|
# Multiple origins can be comma-separated
|
|
CORS_ORIGINS=https://your-domain.com
|