From aed38e4ecaca808ca17db4a148dc93b5ed8aefae Mon Sep 17 00:00:00 2001
From: Arnaud <anelissen@solem.fr>
Date: Wed, 1 Jul 2026 11:59:28 +0200
Subject: [PATCH] Fix Caddy volume mount issue in Portainer

- Remove problematic Caddyfile volume mount that fails in Portainer
- Use Caddy's command-line reverse proxy mode instead
- This avoids file mounting issues while providing same functionality
- Caddy will auto-handle HTTPS/Let's Encrypt for the specified domain
- Simpler, more portable configuration for containerized deployments
---
 docker/docker-compose.deploy.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docker/docker-compose.deploy.yml b/docker/docker-compose.deploy.yml
index c985334..84d1113 100644
--- a/docker/docker-compose.deploy.yml
+++ b/docker/docker-compose.deploy.yml
@@ -112,11 +112,13 @@ services:
       - "80:80"
       - "443:443"
     volumes:
-      - ./Caddyfile:/etc/caddy/Caddyfile
       - caddy_data:/data
       - caddy_config:/config
     environment:
       DOMAIN: ${DOMAIN:-localhost}
+    # Use Caddy's reverse proxy command without file mounting
+    # This avoids Portainer file mount issues
+    command: caddy reverse-proxy --from "${DOMAIN:-localhost}" --to web:3000
     depends_on:
       - web
     networks: