Refine technical documentation to reflect current architecture, component structure, and routing conventions for the vcon console.
1.3 KiB
1.3 KiB
Docker & Coolify Deployment Manifest
Purpose
Production container definitions and orchestration for DataStack's multi-service architecture (docker/):
web(Dockerfile.web): Standalone Next.js 15 frontend,/vcon/*admin console, and REST API on port3000(runs as non-root user).ingestion(Dockerfile.server): Express + Socket.IO real-time ingestion server on port4000(runs as non-root user).proxy(Dockerfile.proxy+coolify-nginx.conf): Nginx reverse proxy on internal port80, forwarding/socket.io/toingestion:4000and web traffic toweb:3000.postgres: PostgreSQL 16 service with persistentpgdatavolume storingadmin_users,admin_login_attempts,client_sdks, andadmin_settings.redis: Redis 7 service with persistentredisdatavolume.
Shared Volumes & Networking
- Both
webandingestionmount thedatastack-datavolume at/app/storage/data, ensuring CSV partitions written by either process are immediately visible across the platform. - Both
webandingestionconnect topostgresviaDATABASE_URLover the private Compose network, synchronizing client registrations, revocation status, and runtime settings automatically. webcommunicates withingestionviaINGESTION_INTERNAL_URL="http://ingestion:4000"for live health metrics and manual buffer flushes.