xDebug VS Predis

Code profiling: Code profiling involves measuring the performance of your code by analyzing the execution time and memory usage of specific functions or methods. You can use a tool like Xdebug or Blackfire to perform code profiling on your Laravel application. To use Blackfire, ensure that your environment meets the following requirements:

xDebug is a powerful PHP debugging and profiling tool. Integrated with many IDEs, it can be used for step-by-step debugging, setting breakpoints, and real-time value inspection, making the debugging process more efficient. (xDebug is already built into ServBay, no need for separate installation)

It is necessaire to active Xdebug on your PHP. More details on Xdebug official documentation.

Is a Docker WordPress Environment focused on the development of WordPress plugins and themes, supports WP-CLI, phpMyAdmin, Xdebug and WordPress Coding Standards - WPCS.

I've gotten a lot of mileage out of Psalm, a static analysis tool that can help you identify potential bugs and things that might not be considered best practice, and XDebug, a debugging and profiling extension for PHP.

Step debugger

XDebug

Details: https://xdebug.org/

Xdebug, per the official website, “is an extension for PHP, and provides a range of features to improve the PHP development experience”.

I am going to connect to redis using the libary predis. Simply add the following to your compose.json

Personally, I prefer Redis for caching. I find it simple and intuitive to work with, using Predis as the connecting client.

That looks like you're connecting to a redis cluster running in cluster mode. The message is directing your client to retry its query on a different shard. You typically need to connect to those using a client/library that is cluster aware. I am not experienced with PHP, but this looks like an option.