Taiga: refactor service naming & resource limits

Add CPU/memory/pids limits for taiga, async, front, gateway, events, async-rabbitmq, events-rabbitmq, manager, and protected. Align manager service usage (was taiga-manage) in admin tasks and inits compose. Switch to variable-driven service names (TAIGA_* vars), add container_name patterns, normalize volume mappings via TAIGA_VOLUME_STATIC/MEDIA, fix depends_on to use TAIGA_* vars, and set RabbitMQ hostnames from vars. Remove obsolete Development.md.

Conversation reference: https://chatgpt.com/share/68da83b7-0cb4-800f-9702-d8a2d4ebea71  (replace with this chat’s share link)
This commit is contained in:
2025-09-29 15:04:12 +02:00
parent 55f2d15e93
commit 27b89d8fb6
6 changed files with 128 additions and 93 deletions

View File

@@ -19,6 +19,50 @@ docker:
enabled: true
taiga:
version: "latest"
cpus: "1.0"
mem_reservation: "1g"
mem_limit: "1.5g"
pids_limit: 512
async:
cpus: "1.0"
mem_reservation: "1g"
mem_limit: "1.5g"
pids_limit: 512
front:
cpus: "0.3"
mem_reservation: "256m"
mem_limit: "512m"
pids_limit: 256
gateway:
cpus: "0.3"
mem_reservation: "256m"
mem_limit: "512m"
pids_limit: 256
events:
cpus: "0.3"
mem_reservation: "256m"
mem_limit: "512m"
pids_limit: 256
async-rabbitmq:
cpus: "1.0"
mem_reservation: "1g"
mem_limit: "1.5g"
pids_limit: 512
events-rabbitmq:
cpus: "0.5"
mem_reservation: "512m"
mem_limit: "1g"
pids_limit: 512
manager:
cpus: "0.5"
mem_reservation: "512m"
mem_limit: "1g"
pids_limit: 256
protected:
cpus: "0.2"
mem_reservation: "128m"
mem_limit: "256m"
pids_limit: 128
server:
csp:
flags: