admin 48ee8be363 tandoor: raise app memory 512M -> 1024M (OOM proven) + correct mem_limit sum ...

tandoor 2.6.13 never reached healthy; gunicorn workers were SIGKILLed in a loop:

  [ERROR] Worker (pid:366) was sent SIGKILL! Perhaps out of memory?
  [ERROR] Worker (pid:367) was sent SIGKILL! Perhaps out of memory?

Separately, .felhom.yml mem_limit was already inconsistent with the compose file:
it claimed 512M while the services summed to 512+256 = 768M. Per the REUSE.md
rule mem_limit is the SUM of the compose limits, so it is now 1024+256 = 1280M.

Campaign 7 catalog sweep.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE

2026-07-19 01:16:21 +02:00

..

.felhom.yml

tandoor: raise app memory 512M -> 1024M (OOM proven) + correct mem_limit sum

2026-07-19 01:16:21 +02:00

docker-compose.yml

tandoor: raise app memory 512M -> 1024M (OOM proven) + correct mem_limit sum

2026-07-19 01:16:21 +02:00