Initializing
Back to Engineering Overview
TECHNICAL BLUEPRINT

DevOps & Infrastructure

VPS setup, Docker containers, Traefik routes, and deploy scripts.

Monthly Uptime Guarantee99.9% Uptime
Let's Encrypt SSL Uptime100% Automated Renewal
Deployment DowntimeZero (Zero-Downtime Reload)
Backup Execution FrequencyDaily Automatic Cron

# Technical Manual: DevOps & Infrastructure Playbook

This playbook documents VPS provisioning protocols, multi-stage Docker builds, Traefik edge routing, and automated remote deploy configurations.

1. Multi-Compose Strategy & Topology

Every production node employs a strictly separated multi-compose strategy to completely isolate stateful infrastructure databases from dynamic application containers.

code
                  [ Public Web User (Port 443) ]


                   [ Traefik Edge Router ]

          ┌─────────────────────┴─────────────────────┐
(Port 4000 Proxy)(Port 3000 Proxy)
     [ API Container ]                           [ Web Container ]
          │                                           │
          └─────────────────────┬─────────────────────┘

                       [ PostgreSQL DB ]
                       (Internal Network Only)

1.1 Docker Compose Environment Separation

  1. Local Development (docker-compose.yml): Spins up ONLY stateful infrastructure mock-ups (PostgreSQL database, Redis cache, Mailhog SMTP tool). Application code runs directly in the host OS to allow instantaneous hot reloading.
  2. Production (infra/docker-compose.prod.yml): Builds application containers, handles Traefik networking labels, and exposes endpoints *internally* to Traefik. Port mappings to the host OS are completely disabled.