Use Coolify-generated database/JWT/admin secrets, assemble DATABASE_URL from the generated DB password, and document the single manual admin email plus rotation requirements.
2.4 KiB
2.4 KiB
Docker Deployment Manifest
Purpose
Production container definitions for the split architecture:
web: standalone Next.js frontend and admin console on port 3000, running as a non-root user.ingestion: Express + Socket.IO process on port 4000, running as a non-root user.proxy: Nginx reverse proxy on internal port 80. Coolify routes the public domain to this service;/socket.io/is forwarded to ingestion and other paths to web.redis: private Compose service reserved for the planned shared-buffer integration; current application code does not consume it.postgres: private Compose service reserved for metadata integration; current application code does not use Prisma at runtime. Collected events must remain in CSV files.
Coolify Compose Deployment
- Create a Git-based Docker Compose application from branch
main. - Set Base Directory to repository root
/and Compose Location todocker/docker-compose.yml. - Set
DATASTACK_ADMIN_EMAILin Coolify. The Compose definition uses Coolify-generatedSERVICE_PASSWORD_64_POSTGRES,SERVICE_REALBASE64_64_JWT,SERVICE_REALBASE64_64_ADMINSESSION, andSERVICE_PASSWORDWITHSYMBOLS_64_ADMIN; it buildsDATABASE_URLfrom the generated PostgreSQL password. - Retrieve the generated
SERVICE_PASSWORDWITHSYMBOLS_64_ADMINfrom Coolify Environment Variables for the initial admin sign-in. JWT/session/admin secrets can be rotated in Coolify. A PostgreSQL password change also requires updating the database role in the existing persistent volume; never paste secrets into Git-tracked files. - Add the public domain to service
proxyat internal port80. Coolify manages proxy labels in its normal Compose mode; do not enable Raw Compose mode or add direct host port mappings. - The
web,ingestion, Redis, and PostgreSQL services are private on the Compose network. Only the proxy is exposed to Coolify's domain proxy. - The
datastack-datanamed volume persists ingestion CSVs;pgdatapersists PostgreSQL files. - The web container does not yet share/read
datastack-data, and neither Redis nor PostgreSQL is wired into runtime code. Those are later roadmap phases, so cross-process reads and metadata durability are not established by these images. - Health checks probe the web landing route, ingestion
/health, proxy route, Redis ping, and PostgreSQL readiness. These checks do not establish application-level shared-storage readiness.