redis-cache | persistent object cache backend for WordPress | Caching library

I am able to solve the issue. Solution is to create a separate docker file to create a tomcat image and used it in docker composer file.

The problem is, even the war is copied to webapps folder of tomcat it wont deploy. See the logs for reference:

clearKey(Book.collection.collectionName) In short, it will clear all the cache for the collection.

In your case this.hashKey = JSON.stringify(options.key || this.mongooseCollection.name); is collectionName

https://redis.io/commands/hget

Returns the value associated with field in the hash stored at key.

You need to set Xdebug's xdebug.client_host to the IP address of your IDE, which you indicated is 192.168.1.150.

You also need to turn off xdebug.discover_client_host, as that would try to use the internal Docker network IP (172.100.0.2), which is not where your IDE is listening on.

Remember: Xdebug makes a connection to the IDE, not the other way around.

ScaleGrid has a blog post to address just this use case: Using Redis Object Cache to Speed Up Your WordPress Installation. Does this help?

From the article, this is the minimal configuration required.

When you call signout, you should not return your own result or view back.

Instead the action method should look like this:

Looks like it's not connectivity issue. Network part you always can check via WebApp->Console and use command

As per to the documentation, here redis does provide basic authentication mechanism,

Exact snippet from the documentation

While Redis does not try to implement Access Control, it provides a tiny layer of authentication that is optionally turned on editing the redis.conf file.

When the authorization layer is enabled, Redis will refuse any query by unauthenticated clients. A client can authenticate itself by sending the AUTH command followed by the password.

Please note, the password will be in plain-text in redis.conf file and is subjected to be viewed by unauthorized parties if they have access to it.

Additionally redis does provide a mechanism to rename or disable specific command, Exact snippet from the same document above ,

it is possible to disable commands in Redis or to rename them into an unguessable name, so that normal clients are limited to a specified set of commands.

Here are some high-level pointers on how to secure a redis deployment

• Bind redis to localhost
• Configure AUTH by enabling requirepass in redis.conf
• Rename or disable dangerous commands

The solution is strange, but simple - remove devtools dependency.

You would need to use an auditIfNotExists or deployIfNotExists policy. The auditIfNotExists will get you started in how to detect resources without diagnostics settings, however there is much more complexity in the deployIfNotExists route that would require more about your specific application in order to address.