From 7b7adbdb34f09b8779a223b26c96cd61078bae5e Mon Sep 17 00:00:00 2001 From: Ty Date: Mon, 21 Sep 2026 01:41:31 -0700 Subject: [PATCH] fix(deploy): nginx client_max_body_size 25m for photo uploads MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Capture→Review uploads the calibrated lineup PNGs (clean cal + batch) as multipart to /api/v1/slabs/{id}/photos. nginx's default 1MB client_max_body_size 413s on real multi-MB photos, blocking the Capture→Review transition. Allow 25m. --- deploy/nginx-m1.conf | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/deploy/nginx-m1.conf b/deploy/nginx-m1.conf index 7a28f6c..43e3a6c 100644 --- a/deploy/nginx-m1.conf +++ b/deploy/nginx-m1.conf @@ -4,6 +4,11 @@ server { root /usr/share/nginx/html; index index.html; + # Capture→Review uploads the calibrated lineup PNGs (clean cal + batch) as + # multipart to /api/v1/slabs/{id}/photos. nginx's default client_max_body_size + # is 1MB, which 413s on real multi-MB photos. Allow large photo bodies. + client_max_body_size 25m; + # Docker embedded DNS for service name resolution (fastapi) resolver 127.0.0.11 valid=10s;