Merge pull request #52 from mcinquin/docker-compose

chore(docker-compose): fix issue with stop_grace_period parameter

Author: mcinquin

README.md

@@ -84,7 +84,7 @@ docker compose up -d
 
 Override via `.env` if needed. See [SECURITY.md](SECURITY.md).
 
-Production-oriented options in Compose include: non-root user, `read_only` root filesystem, dropped capabilities, resource limits, health check on `/api/health`, and log rotation. The reverse proxy stays **outside** Compose (Apache on the host).
+Production-oriented options in Compose include: non-root user, `read_only` root filesystem, dropped capabilities, health check on `/api/health`, and log rotation. **No CPU/RAM cap** by default (a low `mem_limit` / `cpus` makes Next.js feel very slow). The reverse proxy stays **outside** Compose (Apache on the host).
 
 ### Local Docker (build)
 

docker-compose.yml

@@ -17,10 +17,10 @@ services:
       - no-new-privileges:true
     cap_drop:
       - ALL
-    pids_limit: 128
-    mem_limit: 768m
-    cpus: "1.0"
-    stop_grace_period: 30s
+    pids_limit: 256
+    stop_grace_period: "30s"
+    # Pas de mem_limit / cpus : Next.js + SQLite ont besoin de marge ; un plafond
+    # bas (ex. 768m, 1 CPU) provoque lenteur, swap et GC agressif.
     # Écoute uniquement en local ; Apache proxy vers 127.0.0.1:3000
     ports:
       - "127.0.0.1:3000:3000"
@@ -36,7 +36,7 @@ services:
     volumes:
       - ./data:/app/data
     tmpfs:
-      - /tmp:size=64M,mode=1777
+      - /tmp:size=256M,mode=1777
     healthcheck:
       test:
         [