fix(deploy): nginx client_max_body_size 25m for photo uploads
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.
This commit is contained in:
@@ -4,6 +4,11 @@ server {
|
|||||||
root /usr/share/nginx/html;
|
root /usr/share/nginx/html;
|
||||||
index index.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)
|
# Docker embedded DNS for service name resolution (fastapi)
|
||||||
resolver 127.0.0.11 valid=10s;
|
resolver 127.0.0.11 valid=10s;
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user