Redis: REDIS_DB configurable para aislar sesiones entre despliegues
Dos despliegues que comparten el mismo Redis pisaban las sesiones.
session.save_path ahora incluye &database=${REDIS_DB} (default 0).
Despliegue secundario usa REDIS_DB=1.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
dfe3a01fee
commit
7af526e773
+3
-1
@@ -27,8 +27,10 @@ disable_functions =
|
||||
curl.cainfo = /etc/ssl/certs/ca-certificates.crt
|
||||
|
||||
; Session — usar variables de entorno para Redis (Coolify las inyecta)
|
||||
; REDIS_DB separa las sesiones por despliegue (Redis tiene DBs 0-15).
|
||||
; Despliegue A: REDIS_DB=0 (default). Despliegue B: REDIS_DB=1.
|
||||
session.save_handler = redis
|
||||
session.save_path = "tcp://${REDIS_HOST}:${REDIS_PORT}?auth=${REDIS_PASSWORD}"
|
||||
session.save_path = "tcp://${REDIS_HOST}:${REDIS_PORT}?auth=${REDIS_PASSWORD}&database=${REDIS_DB}"
|
||||
session.gc_maxlifetime = 3600
|
||||
session.cookie_httponly = 1
|
||||
session.use_strict_mode = 1
|
||||
|
||||
Reference in New Issue
Block a user