Docs
/
Operations
/
Deployment & Sizing
Production Deployment & Hardware Sizing
Production orchestration guidelines using Docker Compose and Kubernetes, environment variable specifications, automated database migrations, and hardware capacity planning formulas.
1. Environment Configuration
Configure environment files for both frontend and backend before starting container initialization.
PORT=4000 NODE_ENV=production DATABASE_URL="postgresql://hr_admin:SuperSecure2026!@postgres:5432/swot_hr?schema=public" JWT_SECRET="e9a8f27c3d1b4a0f6e5d8c7b9a0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e" RESEND_API_KEY="re_1234567890abcdef" CORS_ORIGIN="https://hr.swotpam.com"
2. One-Command Docker Compose Deployment
The platform includes a zero-configuration Docker Compose stack with PostgreSQL, backend Express, frontend Next.js, and health check monitors.
1
Clone Repository
git clone https://github.com/Ashokvp-05/swot---deploy.git2
Build & Run Containers
docker-compose -f docker-compose.prod.yml up -d --build3
Run DB Migrations & Seed
docker-compose exec backend npx prisma migrate deploy3. Hardware Capacity & Sizing Matrix
| Tier | Active Employees | Recommended CPU | Recommended RAM | Storage (SSD) |
|---|---|---|---|---|
| Starter | 1 – 100 Users | 2 vCPU | 4 GB | 50 GB NVMe |
| Enterprise (Standard) | 100 – 1,000 Users | 4 vCPU | 8 GB | 150 GB NVMe |
| High Scale | 1,000 – 10,000+ Users | 8+ vCPU (Clustered) | 16+ GB | 500 GB NVMe + S3 Vault |
4. Backups & Disaster Recovery
Automated hourly snapshots of PostgreSQL databases with WAL archiving to offsite encrypted cloud object storage (AWS S3 or Cloudflare R2).
Previous
← System Architecture