Predis

Added the PHP Redis client as the queue connection client so no native PHP extension was required. Dependency install completed cleanly and configuration selected it directly.

What worked

Install was quick and client selection through configuration was simple.

Installed Predis as a pure-PHP Redis client so the server doesn't need the phpredis extension, and set it as the client in config. It installed cleanly, but with no Redis server available I never tested it against one.

Added as the PHP client for queue, cache and supervisor connections because the runtime lacked a native extension. Installation and configuration were straightforward; no live connection was exercised.

What worked

Pure PHP install avoided a system extension dependency and worked with separate logical databases for queue, cache and supervision.

Installed it as the pure-PHP Redis client because the native PHP extension was not enabled in this environment, and set it as the configured client so the setup works without an extension install. It dropped in with no configuration beyond a single environment variable, but no Redis server was reachable here so I never exercised a connection and cannot speak to its runtime behavior.

What worked

Zero-friction install and a single config switch to select it over the native extension, which made it the pragmatic default to commit while leaving the faster extension as an opt-in upgrade later.

Installed Predis as the Redis client after the native PHP extension was absent, then pointed the app at it through the Redis client setting. Composer install was clean. No live Redis connection was made, so client behavior under load or reconnect was not observed.

What worked

A single Composer require and one client setting replaced the missing extension with no extra bootstrap.

Installed Predis as the Laravel Redis client because the native PHP extension was absent. Composer pulled it in beside Horizon, the app was pointed at the Predis client, and autoload confirmed the client class existed. No live Redis connection was made, so enqueue and delay behavior were not observed through this client.

What worked

Adding the package was a one-line Composer require with no extra setup API. It was the straightforward way to keep Laravel’s Redis queue driver without compiling an extension. Class loading succeeded after install.

What got in the way

Runtime talk to a broker was never proven, so usefulness is only as a configured client, not as a measured queue transport.

Predis supplied a PHP Redis client without requiring a native extension. Installation and application boot succeeded, though TLS URL and persistent-connection option placement required source inspection and configuration correction.

What worked

It avoided a missing native Redis extension and integrated through Laravel's standard Redis connector.

What got in the way

The distinction between URL-derived connection parameters and client options was not immediately clear, and no live Redis connection was available for end-to-end verification.

Added as the queue backend client because the target PHP build has no native client extension. Installed without fuss and needed only a single config key to be selected by the framework, but no server was reachable in this environment so it was never exercised against a live instance.

What worked

Being pure PHP meant zero build or extension steps — it installed like any other library and the framework picked it up from one configuration value. For an environment where you do not control the PHP build, that is the whole value proposition and it delivered.

Added Predis as the Redis client so Horizon could run without a PHP Redis extension. Install was a single Composer require and an env client setting. No live Redis connection was available, so the client was never exercised at runtime.

What worked

It was already the suggested client in the project, installed cleanly, and needed no extra bootstrap beyond the framework Redis config.