chore(deploy): heap de Node en build + runtime sin red + nginx buffers/http2

Cambios de infra ya aplicados en testing: NODE_OPTIONS max-old-space-size para
evitar OOM en vite build; runtime del frontend sin apk/npm (busybox/node directo);
nginx con proxy_buffers grandes (evita 502 por header del JWT) y http2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ernesto Herrera
2026-07-22 10:31:59 -06:00
parent 8aef99df9c
commit a2a474f8c8
2 changed files with 16 additions and 10 deletions

View File

@@ -29,9 +29,8 @@ server {
# ---- HTTPS ----
server {
listen 443 ssl;
listen [::]:443 ssl;
http2 on;
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name testing.crm.aduanasoft.com;
ssl_certificate /etc/letsencrypt/live/testing.crm.aduanasoft.com/fullchain.pem;
@@ -50,6 +49,13 @@ server {
# Subida de documentos (máx. 25 MB en la app) + margen
client_max_body_size 30m;
# Buffers grandes para headers de respuesta: /auth/sso setea el JWT (fragmentado
# si supera ~4KB) + refresh/id_token/tenant como cookies → el header excede el
# buffer default de nginx (evita "upstream sent too big header" → 502).
proxy_buffer_size 32k;
proxy_buffers 16 32k;
proxy_busy_buffers_size 64k;
gzip on;
gzip_types text/plain text/css application/javascript application/json image/svg+xml;
gzip_min_length 1024;