infra/stacks/reverse-proxy/modules/reverse_proxy
Viktor Barzin 677a181d49
All checks were successful
ci/woodpecker/push/default Pipeline was successful
reverse-proxy: dedicated rate limit for ha-london; bump ha-sofia (cold-client 429s)
New, empty-cache clients (the repurposed Meta Portal running the HA companion
app) cold-load the whole HA frontend at once - dozens of frontend_latest/*.js +
MDI icon chunks. ha-london had no per-service rate limit, so it fell back to the
global 10/s burst 50 and 429'd those chunks, leaving every dashboard blank
(Settings, which loads less, worked). Give ha-london its own 200/500 middleware
(skip_global_rate_limit, mirroring ha-sofia, with depends_on to avoid the
dangling-middleware 404 window) and bump ha-sofia 100/200 -> 200/500 so a cold
Portal load of Sofia doesn't hit the same wall.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 19:53:47 +00:00
..
factory fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip] 2026-06-09 08:45:33 +00:00
main.tf reverse-proxy: dedicated rate limit for ha-london; bump ha-sofia (cold-client 429s) 2026-06-17 19:53:47 +00:00