fixes

docker-compose.yml

@@ -349,8 +349,12 @@ services:
     container_name: nginx
     deploy:
       resources:
+        # cpus:'4' antigo = sem limite real num host de 4 vCPUs (podia
+        # monopolizar a máquina e faminar PHP-FPM/Node dos outros apps
+        # sob carga de TLS/QUIC). Proxy reverso não precisa da máquina
+        # inteira; 2 cores é generoso e deixa margem pros apps.
         limits:
-          cpus: '4'
+          cpus: '2'
           memory: 2G
         reservations:
           cpus: '0.5'
@@ -1114,8 +1118,17 @@ services:
   wordpress:
     image: wordpress:latest
     container_name: wordpress
+    deploy:
+      resources:
+        limits:
+          cpus: '1'
+          memory: 768M
+        reservations:
+          cpus: '0.25'
+          memory: 256M
     volumes:
       - ./docker/wp-content:/var/www/html/wp-content
+      - ./docker/wordpress/uploads.ini:/usr/local/etc/php/conf.d/uploads.ini:ro
     environment:
       - LETSENCRYPT_HOST=www.martinsevieira.adv.br,martinsevieira.adv.br
       - WORDPRESS_DB_NAME=wordpress
@@ -1123,7 +1136,12 @@ services:
       - WORDPRESS_DB_HOST=10.15.0.42
       - WORDPRESS_DB_USER=root
       - WORDPRESS_DB_PASSWORD=34641747
-      - WORDPRESS_CONFIG_EXTRA=define('WP_REDIS_HOST', '10.15.0.55'); define('WP_REDIS_PORT', 6379); define('WP_REDIS_DATABASE', 1); define('WP_CACHE_KEY_SALT', 'wp_mv_adv_'); define('DISABLE_WP_CRON', true);
+      # WP_CACHE precisa estar "true" para o WordPress carregar o
+      # object-cache.php do plugin Redis — sem essa constante o Redis
+      # fica configurado mas o cache de objeto nunca entra em ação, e
+      # toda visita bate direto no MariaDB. Provavelmente a causa
+      # principal do WordPress "meio lento".
+      - WORDPRESS_CONFIG_EXTRA=define('WP_CACHE', true); define('WP_REDIS_HOST', '10.15.0.55'); define('WP_REDIS_PORT', 6379); define('WP_REDIS_DATABASE', 1); define('WP_CACHE_KEY_SALT', 'wp_mv_adv_'); define('DISABLE_WP_CRON', true);
     depends_on:
       - mariadb
     restart: always
@@ -1167,6 +1185,22 @@ services:
       POSTGRES_USER: ${POSTGRES_USER:-anatomia}
       POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-anatomia}
       POSTGRES_DB: ${POSTGRES_DB:-anatomia}
+    # Ajustado ao limite de 512M do container (padrão do Postgres é
+    # pensado para bare-metal com bem mais RAM disponível: shared_buffers
+    # de 128MB e sem effective_cache_size customizado deixa o planner
+    # pessimista sobre quanto cabe em cache).
+    command:
+      - postgres
+      - -c
+      - shared_buffers=128MB
+      - -c
+      - effective_cache_size=384MB
+      - -c
+      - work_mem=8MB
+      - -c
+      - maintenance_work_mem=32MB
+      - -c
+      - max_connections=50
     volumes:
       - anatomia_db_data:/var/lib/postgresql/data
     healthcheck:
@@ -1179,7 +1213,10 @@ services:
     deploy:
       resources:
         limits:
+          cpus: '1'
           memory: 512M
+        reservations:
+          cpus: '0.1'
 
   anatomia-api:
     container_name: anatomia-api
@@ -1204,7 +1241,10 @@ services:
     deploy:
       resources:
         limits:
+          cpus: '1'
           memory: 512M
+        reservations:
+          cpus: '0.25'
 
   anatomia-web:
     container_name: anatomia-web
@@ -1229,6 +1269,7 @@ services:
     deploy:
       resources:
         limits:
+          cpus: '0.5'
           memory: 256M
 
   # One-off data pipeline: generates the seed GLB models + populates the DB.