From 0c6b6c5cadfd072ec7765ec4917d2883f89bca9e Mon Sep 17 00:00:00 2001
From: Leon Serfaty <80597822+silkoserfo@users.noreply.github.com>
Date: Mon, 7 Sep 2026 11:52:14 -0400
Subject: [PATCH] fix(deploy): attach compose services to dokploy-network
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Dokploy's managed Postgres runs as its own service on the shared
`dokploy-network`. The compose stack only had its own default network, so
web and worker could not resolve the database host — `prisma migrate deploy`
failed on boot and both containers crash-looped.

Join both services to `dokploy-network` while keeping `default` for
web<->worker traffic.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 docker-compose.yml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docker-compose.yml b/docker-compose.yml
index 2b97749..5319b8e 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -27,6 +27,11 @@ services:
       UMAMI_WEBSITE_ID: ${UMAMI_WEBSITE_ID:-}
     volumes:
       - storage:/app/storage
+    # `default` keeps web<->worker talking; `dokploy-network` is where Dokploy's
+    # managed Postgres service lives, so Prisma can resolve the DB host.
+    networks:
+      - default
+      - dokploy-network
     expose:
       - "3000"
     # Dokploy attaches the Traefik router (domain + SSL) to this service on port 3000.
@@ -39,8 +44,16 @@ services:
       STORAGE_DIR: /app/storage
     volumes:
       - storage:/app/storage
+    networks:
+      - default
+      - dokploy-network
     depends_on:
       - web
 
 volumes:
   storage:
+
+# Created by Dokploy; every managed service (incl. Postgres) is attached to it.
+networks:
+  dokploy-network:
+    external: true