Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(migration): list REDIS_TLS in the external Redis recipe
Yudhi Armyndharisd6c9e14d6aa7
diff --git a/docs/14-migration-guide.md b/docs/14-migration-guide.mdindex e8a9d8f50..91266fb3a 100644--- a/docs/14-migration-guide.md+++ b/docs/14-migration-guide.md@@ -304,6 +304,7 @@ REDIS_HOST=your-redis-host.comREDIS_PORT=6379REDIS_USERNAME=optionalREDIS_PASSWORD=optional+REDIS_TLS=false # true for a managed Redis that requires TLS```> Setting `REDIS_BUILTIN` in `.env` **pins** it: the env value wins, so the dashboard's built-in@@ -315,8 +316,9 @@ REDIS_PASSWORD=optional> This applies to a bare-metal install that reads the project `.env`. Compose does not forward> `REDIS_BUILTIN` (nor `POSTGRES_BUILTIN` or `MINIO_BUILTIN`), so on compose clear "Use Built-in Redis> Container" in Dashboard > Infrastructure (or set `REDIS_BUILTIN=false` in `data/.env.generated`), and-> put only the forwarded `REDIS_ENABLED`, `REDIS_HOST`, `REDIS_PORT`, `REDIS_USERNAME` and-> `REDIS_PASSWORD` in the `.env` next to `docker-compose.yml`.+> put only the forwarded `REDIS_ENABLED`, `REDIS_HOST`, `REDIS_PORT`, `REDIS_USERNAME`,+> `REDIS_PASSWORD`, `REDIS_TLS`, `REDIS_CONNECT_TIMEOUT_MS` and `REDIS_CACHE_DB` in the `.env` next+> to `docker-compose.yml`.| Scenario | Support | Notes || ------------------------- | ------- | ------------------------------------------ |