Issue setting cache driver to redis

[borgarlie]

Hi,

We are debugging an issue with the fetching job getting terminated, and when trying to look at the cache value for the mutex (from code) it is always null, however it does not start a new job until the FETCH_MAX_EXECUTION_TIME times out. So there is something weird going on there.

We decided to try to use redis cache instead of file cache, so that it would become possible to actually inspect the cache properly. But setting these environment variables does not do anything:

CACHE_DRIVER=redis
REDIS_HOST=tls://RESOURCE_NAME.redis.cache.windows.net
REDIS_PASSWORD=password
REDIS_PORT=6380

Is this not supported out of the box? Any hints to what we would have to do? Or is this the wrong place to ask?

[tiredofit]

Hi this would make sense in the upstream Freescout repository to the developers. Theoretically this should work, and would probably increase performance as well with being able to change session, cache and others to redis. If you do manage to get it working I can build it into this Docker image with easily controllable env vars for others to benefit.