viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

tripit: dedicated 100/1000 rate-limit — photo grid 429s on the default 10/50
Some checks failed
ci/woodpecker/push/build-cli Pipeline was canceled
Details
ci/woodpecker/push/default Pipeline was canceled
Details

Browse source 
Viktor hit a wall of 429s scrolling the new trip Photos tab: every Immich
thumbnail proxies through tripit's /api, so a few-hundred-photo trip is
that many parallel GETs from one IP — far past the shared Traefik
limiter's average 10 / burst 50. Fourth instance of the parallel-asset
pattern (ha-sofia, ActualBudget, noVNC); same cure: dedicated
tripit-rate-limit middleware (average 100, burst 1000) +
skip_default_rate_limit on the main tripit ingress only. The token-gated
calendar/email/slack carve-outs keep the strict default.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-06-12 19:15:56 +00:00
parent e8a4eb0f05
commit eef4dc7f63
2 changed files with 31 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
stacks/tripit/main.tf
View file

@ -760,6 +760,12 @@ module "ingress" {
name = "tripit"
port = 8080
tls_secret_name = var.tls_secret_name
# The Photos tab proxies Immich thumbnails through /api — a trip-gallery
# scroll is hundreds of parallel image GETs, far past the default 10/50
# limiter. Dedicated 100/1000 middleware (stacks/traefik middleware.tf);
# the calendar/email carve-out ingresses below stay on the default.
skip_default_rate_limit = true
extra_middlewares = ["traefik-tripit-rate-limit@kubernetescrd"]
}
# Calendar feed carve-out for the same host: path /api/calendar served by the