That may sound as a simple question.. At the moment I simply added Redis as driver for my pages cache but how do I know if it’s actually well working on my prod server? It’s a managed one (infomaniak) and all I know is that Redis is installed.
It’s a bit of a black box right now and I’d love to know if all is working fine.
Also, in Kirby’s reference page about cache it says that I can also cache on uuid but not sure how important is that and if I should do it or not.
Just my 2c… unless you have more than 4k pages using Redis will not measurably improve your performance since the server will keep the content files and UUID cache files “hot” in disk cache RAM and thus as quick as Redis.
In regard to Redis you can create custom plugin, make it have a cache living on Redis and then create and read cache values.
Or if your host provides you with an URL use a tool like TablePlus.
I have no experience with Redis but regarding the bot traffic: the last 1k+ pages site I launched also saw tremendous traffic spikes caused by (AI) scraper bots. So I added an Nginx server directive that checks the user agent string against a list of known bots and drops the connection (444) on a match. Still evaluating but so far it seems to be working.
That could help, but I find a lot of the bad faith crawlers ignore robots.txt. I’m also seeing crawlers use stealth methods like using an MS Edge user agent string, have a delay of a few seconds between each request and do batch runs of 100 requests, against which even my method doesn’t work.