You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't see how to make this work with the flask-cacheredis config keys.
I started digging through the source, flask-cache uses werkzeug RedisCache, whose docs say: The first argument can be either a string denoting address of the Redis server or an object resembling an instance of a redis.Redis class.
So it's actually possible to create a StrictRedis instance and pass it to flask-caches CACHE_ARGS in the CACHE_REDIS_HOST option.
It works, it just seems a little ...undocumented?
All that said, I don't quite see how to use the Custom Cache Backends described in flask-cache docs here, so perhaps there's a way to do similar there.
Thanks for any help!
The text was updated successfully, but these errors were encountered:
RedCraig
changed the title
connecting to an SSL redis instance
connecting to an SSL StrictRedis instance for caching
Apr 21, 2016
This isn't an issue per-se, just something that took me a while to figure out - and I wanted to check the way I'm doing this is OK.
I want to connect to an instance of the microsofts redis cache in azure.
They require an ssl connection, example uses StrictRedis connection:
I couldn't see how to make this work with the
flask-cache
redis config keys.I started digging through the source,
flask-cache
uses werkzeug RedisCache, whose docs say:The first argument can be either a string denoting address of the Redis server or an object resembling an instance of a redis.Redis class.
So it's actually possible to create a StrictRedis instance and pass it to
flask-cache
sCACHE_ARGS
in theCACHE_REDIS_HOST
option.It works, it just seems a little ...undocumented?
All that said, I don't quite see how to use the Custom Cache Backends described in
flask-cache
docs here, so perhaps there's a way to do similar there.Thanks for any help!
The text was updated successfully, but these errors were encountered: