-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning with redis storage: You're running Souin with the default storage that is not optimized and for development purpose #102
Comments
Hello @bgeneto do you have some error logs above? If Souin/cache-handler fallbacks on the default storage, that's because it couldn't connect to the redis instance. Is your keydb reachable? |
Unfortunately there is no fallback log message. Only messages below. I'd tried hard to make it work...
I don't know... I think that it is not falling back but not detecting the storage plug-in...
Yes. It is...
|
It follows a minimal Dockerfile, compose.yaml and Caddyfile to test... https://drive.google.com/file/d/1tFvsq_rxU5aav6ViR-38-693kWAOl3yw/view?usp=sharing Thanks for your help! |
@bgeneto I found the bug The check about the storages to use and the generated Uuid to identify redis weren't good. That should work, you can already use it RUN xcaddy build --with github.com/caddy-dns/cloudflare \
--with github.com/darkweak/storages/go-redis/caddy \
--with github.com/darkweak/souin@v1.7.1=github.com/darkweak/souin@5a79ab7fe694a33db6dc6014d79834cbb363bc5f \
--with github.com/darkweak/souin/plugins/caddy@5a79ab7fe694a33db6dc6014d79834cbb363bc5f |
I'm getting this warning message after having compiled the latest cache handler version, even though I'm using Redis storage (see Dockerfile below):
Here is the Dockerfile used to build the image...
And below is the relevant global cache config in my Caddyfile:
It used to work previously, are there any breaking changes? TIA.
The text was updated successfully, but these errors were encountered: