feat: add Coolify deployment proxy

Route the Coolify HTTPS domain through an internal Nginx proxy to Next.js and Socket.IO. Keep app/backing services private, preserve local development socket URLs, and document Coolify Compose setup.
This commit is contained in:
i vib committed 2026-10-23 20:53:34 -07:00
1 parent fcc4f4db2d
commit e52e25e990
6 files changed
+92 -21

No files matched your search

+24 -4
View File
@@ -4,8 +4,8 @@ services:
build:
context: ..
dockerfile: docker/Dockerfile.web
ports:
- "3000:3000"
expose:
- "3000"
environment:
NODE_ENV: production
PORT: "3000"
@@ -33,8 +33,8 @@ services:
build:
context: ..
dockerfile: docker/Dockerfile.server
ports:
- "4000:4000"
expose:
- "4000"
volumes:
- datastack-data:/app/storage
environment:
@@ -55,6 +55,26 @@ services:
retries: 3
start_period: 10s
# Coolify routes the public domain to this service on its internal port 80.
proxy:
build:
context: ..
dockerfile: docker/Dockerfile.proxy
expose:
- "80"
depends_on:
web:
condition: service_healthy
ingestion:
condition: service_healthy
restart: unless-stopped
healthcheck:
test: ["CMD-SHELL", "wget -q -O /dev/null http://127.0.0.1/ || exit 1"]
interval: 30s
timeout: 5s
retries: 3
start_period: 10s
# Reserved for the planned shared buffer integration; not consumed by the current runtime.
redis:
image: redis:7-alpine