README: raise traefik's read timeout with rproxy's for large git pushes
check / check (push) Waiting to run

The commented rproxy lines said a git push may take up to 10 minutes to
send, but traefik v3 gives a whole request, body included, 60 seconds by
default, and answers 502 to a slower one. A commented traefik line now
raises its readTimeout to match.

Model: opus-5-5
This commit is contained in:
sneak committed 2026-11-19 08:51:32 +00:00
1 parent 3222c55009
commit 5b5a12e57c
1 file changed
+5 -1
+5 -1
View File
@@ -476,6 +476,9 @@ services:
- --certificatesResolvers.le.acme.email=hostmaster@example.com
- --certificatesResolvers.le.acme.storage=/letsencrypt/acme.json
- --certificatesResolvers.le.acme.tlsChallenge=true
# Give a request 10 minutes to arrive, rather than 1, for the
# large git pushes the rproxy lines below accept.
# - --entryPoints.websecure.transport.respondingTimeouts.readTimeout=600s
ports:
- "80:80"
- "443:443"
@@ -495,7 +498,8 @@ services:
SWW_RPROXY_WAF_BACKEND: http://waf:8080
SWW_RPROXY_UPSTREAM_URL: http://app:3000
# Accept git pushes up to 1 GiB, rather than 100 MiB, sent in
# up to 10 minutes, rather than 1.
# up to 10 minutes, rather than 1, with traefik's readTimeout
# line above.
# SWW_RPROXY_MAX_REQUEST_SIZE: 1G
# SWW_RPROXY_MAX_REQUEST_TIME_MS: "600000"
labels: