feature request: Redis config no way to select redis database

[l3126596029]

What problem did you meet?

In Logto v1.42.0, when using Redis there's no way to specify which Redis database (DB index) to use — even adding /1 to the connection parameter doesn't take effect. It would be great if the next version could support specifying the Redis database.eg:redis://:password@Redis/1

Describe what you'd like Logto to have

In Logto v1.42.0, when using Redis there's no way to specify which Redis database (DB index) to use — even adding /1 to the connection parameter doesn't take effect. It would be great if the next version could support specifying the Redis database.eg:redis://:password@Redis/1

[wangsijie]

Hi @l3126596029 — redis://:password@redis:6379/1 should actually work on standalone Redis; Logto passes REDIS_URL straight to node-redis, which issues SELECT 1 on connect (verified on the wire with the pinned client version).

Does your URL contain ?cluster=1? Redis Cluster only supports DB 0, so the index gets dropped there. If not, could you share the startup log line (Connected to Redis vs No Redis client initialized, skipping) and how you checked?

[l3126596029]

Hi My Logto console's log:
cache info Connected to Redis core info Core app is running at http://localhost:3001/ core info Core app is running at https:/// admin info Admin app is running at http://localhost:3002/ admin info Admin app is running at https:/// fp0xYGb6f4WsGX8X <-- GET / tenant info Init tenant: default Custom domain: undefined cache info Well-known cache hit for, default, sie, #

---

This's redis environment variable: REDIS_URL=redis://:password@Redis/1
then I checked the Redis database and found no cached data for logto in database 1, but 0 have

[wangsijie]

The logs actually show the connection succeeded, and the Well-known cache hit line is served from whichever DB the client is connected to. Since your data is in DB 0, the running container's REDIS_URL almost certainly doesn't have /1 — if the SELECT had failed, you'd see No Redis client initialized, skipping instead.

Please check:

1. docker exec <logto-container> printenv REDIS_URL — the change likely wasn't applied because the container wasn't recreated (docker restart doesn't reload env).
2. redis-cli CLIENT LIST — the db= field of the Logto connection shows which DB it's on.