Weave Code
Phpredis Bundle Laravel Package
pompdelux/phpredis-bundle
A Symfony bundle that integrates the phpredis PHP extension with configurable Redis client services, connection management, and dependency injection, making it easy to use Redis for caching, sessions, queues, and pub/sub in Symfony applications.
phpredis-bundle integrates the native phpredis PHP extension into Symfony applications, exposing Redis connections as configurable services through the framework's dependency injection container. It wraps \Redis clients so you can define connections in YAML or PHP configuration and inject them wherever needed, instead of instantiating them manually.
- Configurable connection definitions managed through the Symfony service container
- Direct use of the phpredis extension for lower overhead than pure-PHP clients
- Autowiring-friendly service aliases for cleaner controller and service signatures
- Support for multiple named connections in a single application
- Standard Symfony bundle structure for straightforward registration and environment-specific settings
Note that this package has few users and limited documentation; review the source before relying on it in production.
Frequently asked questions about Phpredis Bundle
- Does pompdelux/phpredis-bundle work with Laravel?
- No. It is a Symfony2 bundle for phpredis integration, not a Laravel package, and the available description does not declare Laravel service-provider support. For Laravel applications, use the framework's Redis configuration with phpredis or Predis instead of installing this bundle.
- How do I install phpredis-bundle in a Symfony application?
- Install it with Composer using composer require pompdelux/phpredis-bundle, then register the bundle in your Symfony kernel and add the bundle configuration for your Redis connections. The package targets Symfony2-era applications, so confirm its Composer constraints match your Symfony version before installing. After installation, clear the cache and verify the Redis service is available in the container.
- What PHP extension does this package require?
- It integrates the native phpredis extension, so the Redis extension for PHP must be installed and enabled. Verify with php -m or phpinfo that redis is loaded in every environment, including CLI and web SAPIs. Without the extension, the bundle's Redis client wiring will not work.
- Which Symfony and PHP versions are supported by pompdelux/phpredis-bundle?
- The repository describes it as a Symfony2 bundle, and the available release evidence only covers 1.0.2. Composer constraints, the PHP support matrix, and tested Symfony versions were not supplied in the evaluation metadata. Check the package's composer.json and CI configuration before adopting it in a modern Symfony or PHP 8 application.
- How do I configure Redis connections, clients, and caching with this bundle?
- The bundle centralizes Redis configuration and service wiring so you can define connections and clients through Symfony configuration rather than instantiating phpredis objects manually. Exact configuration keys should come from the package README or bundle extension class because the available excerpt does not document them. Validate the resolved service definitions in the container after configuring.
- What changed in version 1.0.2 of phpredis-bundle?
- The 1.0.2 release note says it fixes a wrong exception class name. That is a patch-level behavioral change: the exception type thrown on error paths may now differ from earlier 1.0.x releases. Applications that catch, log, or filter by the old class name should be reviewed.
- Could the 1.0.2 exception class fix break my error handling?
- It can if your code catches the previously incorrect exception class by its fully qualified name, or if your exception handler, logging, or alerting rules reference that class. Search catch blocks, instanceof checks, $dontReport/$levels-style maps, and error-tracking filters for the old name. Where possible, catch a stable parent interface or base exception instead of the specific class.
- Is pompdelux/phpredis-bundle safe to use in production?
- The 1.0.2 patch is low structural risk because it adds no features, deprecations, or declared breaking changes. The residual risk is behavioral and concentrated in error handling, plus unverified package metadata such as license, maintainer activity, and CI coverage. Test in a non-production environment, exercise an error path, and canary before a full rollout.
- How does phpredis-bundle compare with using phpredis directly or Predis?
- The bundle adds Symfony configuration and service wiring on top of the native phpredis extension, reducing manual client setup in Symfony applications. Using phpredis directly gives you fewer layers but more boilerplate; Predis is a pure-PHP client that avoids the extension requirement. For Laravel, the framework's own Redis integration is the more appropriate choice.
- Is the package actively maintained and does it have tests?
- Maintainer activity, release cadence, test coverage, and static analysis were not supplied in the available metadata, so they must be verified on the repository. The only cited evidence is the 1.0.2 release note, which is not enough to judge long-term maintenance. Pin to ^1.0 and subscribe to releases while you validate CI and changelog coverage.
Weaver
How can I help you explore Laravel packages today?