Hey Builders of Retool,
in "Settings" > "Debug Info" > "On Prem Environment", I can see several Redis related "unset variables", esp.
REDIS_USER_CACHE_HOST
REDIS_USER_CACHE_PORT
REDIS_USER_CACHE_DB
REDIS_USER_CACHE_PASSWORD
RETOOL_RPC_REDIS_HOST
RETOOL_RPC_REDIS_PORT
RETOOL_RPC_REDIS_DB
RETOOL_RPC_REDIS_PASSWORD
WORKFLOW_REDIS_HOST
WORKFLOW_REDIS_PORT
WORKFLOW_REDIS_DB
WORKFLOW_REDIS_PASSWORD
These are not documented in
Could you please share more details and documentation how these different caches work? Which are recommended to configure? Is it recommended to use separate DBs if we use more than just the main cache? Are there conventions for the DBs?
Best Michael
1 Like
Hi @michael_h, good question! We don't have additional documentation for those environment variables at this time, but only because setting them isn't something that's broadly recommended. The main Redis environment variables should meet most demands, that is to say that the env vars you see documented would effectively replace any use cases in our code base for the additional unset env vars you found.
I can share some details though. The Redis user cache env vars would be for setting up a separate Redis database, in the case that you had so many concurrent users that the reading and writing of user info into the cache was interfering with other info that you wanted available in the cache. The same argument could be made for using the Retool RPC env vars.
Unlike those situations however, a quick look at the code base reveals that the workflow Redis env vars are declared but aren't implemented anywhere.
All that is to say that you shouldn't need to worry about any of the unset env vars you find unless you had an especially unique situation that called for it. 
1 Like
Thanks a lot for looking into it and for the explanations, @Mike_M
It's highly appreciated.
1 Like