Production Deployment
This section covers deploying Triage Warden in production environments.
Deployment Options
Triage Warden can be deployed in several ways:
- Docker - Recommended for most deployments. Quick setup with Docker Compose.
- Kubernetes - For orchestrated, scalable deployments using raw manifests.
- Helm Chart - Recommended for Kubernetes. Templated deployment with environment-specific values.
- Binary - Direct binary installation on Linux servers.
Before You Deploy
Before deploying to production, review:
- Production Checklist - Security and configuration requirements
- Configuration Reference - All environment variables and settings
- Database Setup - PostgreSQL configuration for production
- Security Hardening - TLS, secrets, network policies
- Scaling - Horizontal scaling considerations
Quick Start
For a quick production deployment with Docker:
# Clone the repository
git clone https://github.com/your-org/triage-warden.git
cd triage-warden/deploy/docker
# Configure environment
cp .env.example .env
# Edit .env with your settings
# Generate encryption key
echo "TW_ENCRYPTION_KEY=$(openssl rand -base64 32)" >> .env
# Start services
docker compose -f docker-compose.prod.yml up -d
Architecture Overview
A typical production deployment includes:
┌─────────────────┐
│ Load Balancer │
│ (TLS term.) │
└────────┬────────┘
│
┌──────────────┼──────────────┐
│ │ │
┌─────▼─────┐ ┌─────▼─────┐ ┌─────▼─────┐
│ Triage │ │ Triage │ │ Triage │
│ Warden │ │ Warden │ │ Warden │
│ Instance 1│ │ Instance 2│ │ Instance 3│
└─────┬─────┘ └─────┬─────┘ └─────┬─────┘
│ │ │
└──────────────┼──────────────┘
│
┌────────▼────────┐
│ PostgreSQL │
│ (Primary) │
└─────────────────┘
Support
For deployment assistance:
- Check the Troubleshooting Guide
- Review GitHub Issues
- Contact support at [email protected]