Valkey GLIDE PHP Client

Agent-facing skill for GLIDE PHP. Assumes the reader can already write PHPRedis from training (new Redis(), $r->connect($host, $port), positional command args). Covers only what GLIDE diverges on and what GLIDE adds on top.

Separate repository: valkey-io/valkey-glide-php (v1.0.0 GA).

Routing

Question	Reference
`ValkeyGlide` vs `ValkeyGlideCluster` construction divergence (standalone needs explicit `connect()`; cluster config goes in `__construct`), TLS, auth, IAM, read_from, reconnect strategy, `registerPHPRedisAliases()`	connection
Array-and-callback `subscribe(array, callable)` / `psubscribe(array, callable)` - REVERSED shape from PHPRedis varargs; `ssubscribe` NOT implemented in v1.0.0; `unsubscribe(?array)`; introspection via `pubsub()`	pubsub
Install via PIE/PECL/Composer, PHP 8.2/8.3 only, supported platforms, command groups, batching (MULTI/EXEC + pipeline), error model (`ValkeyGlideException`), password rotation	overview

Multiplexer rule

One ValkeyGlide / ValkeyGlideCluster instance is the shared multiplexer for a PHP process (long-running CLI, daemon, or FPM worker). Do not create per-request clients inside the same process. Do not pool multiple instances against the same node. The Rust core pipelines concurrent calls across the multiplexed connection.

Exceptions that need a dedicated client instance: