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
We run a 3 server Redis Sentinel cluster which is shared between a laravel app and also a java application.
Presently right now, database 0 is used for the java web application with the remaining databases being laravel. Below are the configuration settings from our laravel env file:
We have a few new laravel jobs which we need to delete/remove a cached key set by the java application. The redis prefix in the java application is not set, but the prefix is auto-added with the default laravel configuration for redis database/cache config files.
What would be the best way for laravel to access these "java application set keys" in Redis?
We did try creating another database config setting under redis area but it throws errors in production that it isn't defined. Extra cache attribute added:
Do we need a hybrid setup per your readme front page -- granted after reading it a couple of times, I am not sure I understand what to change though unfortunately.
Thanks for your help & feedback!
The text was updated successfully, but these errors were encountered:
We run a 3 server Redis Sentinel cluster which is shared between a laravel app and also a java application.
Presently right now, database 0 is used for the java web application with the remaining databases being laravel. Below are the configuration settings from our laravel env file:
We have a few new laravel jobs which we need to delete/remove a cached key set by the java application. The redis prefix in the java application is not set, but the prefix is auto-added with the default laravel configuration for redis database/cache config files.
What would be the best way for laravel to access these "java application set keys" in Redis?
We did try creating another database config setting under redis area but it throws errors in production that it isn't defined. Extra cache attribute added:
Do we need a hybrid setup per your readme front page -- granted after reading it a couple of times, I am not sure I understand what to change though unfortunately.
Thanks for your help & feedback!
The text was updated successfully, but these errors were encountered: