modcomms/.env.deploy.example
michael 99af0164e6 Add PostgreSQL database support with Alembic migrations
Backend:
- Add PostgreSQL service to docker-compose with health checks
- Add SQLAlchemy async models for all entities (Agency, User, Campaign,
  Proof, ProofVersion, FlaggedItem, ResolvedItem, ErrorItem)
- Add Alembic migration framework with initial schema migration
- Add repository layer for CRUD operations
- Add REST API endpoints for campaigns, proofs, and audit items
- Add file storage service for proof uploads
- Update WebSocket handler to optionally persist analysis results

Frontend:
- Add apiService.ts for REST API communication
- Update geminiService.ts to support database persistence options

Deployment:
- Update deploy.sh to handle database migrations (6-step process)
- Update Dockerfile to include alembic configuration
- Add PostgreSQL environment variables to .env templates

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-16 12:27:18 -06:00

37 lines
1.3 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
# 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
# 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