Release v4.2.5

[github-actions[bot]]

View CHANGELOG.md for details

---

This discussion was created from the release Release v4.2.5.

[kryjex]

Hello,
This version is not in npm yet right?

[stafyniaksacha]

@kryjex Should be done!

[kryjex]

Thanks!

[BabyDino]

@stafyniaksacha Can you release this to npm please?

[stafyniaksacha]

@stafyniaksacha Can you release this to npm please?

Thanks for the ping, it's published!

[IgorBadanyuk]

Hi. I know it's off topic. While there were no updates I was sitting on this wonderful plugin. I needed to solve 2 problems that are not solved at the moment.

User cache.
Cache in cluster mode without redis and in-memory using SQLite3 memory cache.

1. The solution is not perfect but it works. To make user's request unique you need to add userId to get request. I did this with route params like /favorites/userId. But here immediately appears the security problem because user can change the id and steal someone else's cache. To that I added a small patch which checks if userId is there then it is necessary to verify the token which is still attached and after that verify the cache request. Verification is still faster than getting userId data every time. On average it takes 100ms to get the user after the caching 26ms.

2. For WIN and even linux it is not easy to install and configure Redis. Since you are using node-cache-manager there is a node-cache-manager-sqlite provider for it. As a test, I modified the standard in-memory and upgraded node-manager to 4.1.0. I also installed cache-manager-sqlite and sqlite3. The problem I encountered is that cache-manager-sqlite doesn't have a keys function to list all the keys as described in your CacheProvider interface. But with the same very small patch I fixed it. The result is that SQLite3 runs in inmemory mode with caching flag, which means no matter how many instances of Strapi they will communicate with single storage, as in Redis. In terms of performance there is no huge difference +- 3-4 milliseconds.

My point is that I could try to PR into this library to add a keys function or make a branch from it. This provider is simple under the hood, the provider code for the plugin is pretty much the same. Then we would have an opportunity to add a 4 provider SQLite3.

[stafyniaksacha]

Hey Igor!

Upgrading node-manager to latest version is a good thing, but I think it will introduce breaking change on the configuration. We should either release also a breaking change with a migration guide, or to seamlessly convert the old configuration.

Clustering is a huge topic, that would be great that this plugin covers it. What do you think about creating a new provider for this? So the function to list all the keys should be implemented on this provider?

I let you create a PR for that, would be a great improvment!