- Can I use m6web/redis-bundle in a Laravel application?
- No, not in any practical sense. m6web/redis-bundle is a Symfony bundle whose entire integration surface is a Bundle subclass, a dependency injection extension, a semantic configuration tree and compiler passes, none of which Laravel boots. Composer may install it, but the m6web_redis config keys, service aliases, session handler and profiler collector are all kernel-coupled and will never load. For Laravel, configure named Redis connections in config/database.php and resolve them with Illuminate\Support\Facades\Redis or the injected Redis factory.
- How do I install m6web/redis-bundle?
- In a Symfony application you run composer require m6web/redis-bundle, register the bundle in your kernel (or bundles.php on Symfony Flex), then declare your servers and clients under the m6web_redis configuration key. Clients become available as autowirable services through the bundle's aliases. There is no Laravel service provider or config publishing step, so the install instructions do not translate to a Laravel app.
- Does m6web/redis-bundle support Laravel 10 or Laravel 11 and PHP 8.2?
- There is no stated support for PHP 8.2 or 8.3, and the package's last release was in 2022, so modern Laravel versions are untested at best. It hard-depends on symfony/framework-bundle, symfony/dependency-injection and symfony/config, which overlap with the Symfony components Laravel itself pulls in and can create solver conflicts. Before considering any reuse, run composer why-not with your target Laravel and PHP matrix to see whether the constraints resolve. In practice the answer is to use Laravel's native Redis support rather than trying to make this bundle fit.
- How does m6web/redis-bundle configure multiple Redis connections and clients?
- You declare servers, clusters and per-client options in YAML under the bundle's configuration root, and the extension builds Predis client services you can inject by alias. This lets one application talk to several Redis instances with different prefixes, serializers or topologies. Laravel covers the same need with multiple named connections in config/database.php and Redis::connection('name'). The YAML-driven service wiring itself is the part that is Symfony-specific and not reusable.
- Does m6web/redis-bundle support Redis clusters and master/slave replication?
- Yes, the bundle exposes cluster and master/slave topologies through its Predis configuration, which is the only genuinely interesting capability underneath the Symfony glue. Laravel's Redis manager also supports cluster connections and passes options through to Predis, including replication and sentinel settings. If a specific topology feature is truly missing from illuminate/redis, vendor the relevant factory classes rather than adopting the whole bundle.
- Can m6web/redis-bundle be used for session storage and caching?
- In Symfony it registers a Redis-backed session handler and cache services, which is part of its stated purpose alongside connection management. Those registrations are tied to Symfony's session and cache component interfaces, so none of that glue is usable from Laravel. Laravel already ships redis session and cache drivers configured through config/session.php and config/cache.php. Use those instead of reimplementing the bundle's glue.
- What does the m6web/redis-bundle profiler data collector do, and is it safe in production?
- It adds a Symfony toolbar panel that records the Redis commands issued during a request, which is useful for debugging in development. Like most data collectors it should be disabled or restricted outside dev and staging, since it retains per-command data on the request hot path. Under Laravel the equivalent visibility comes from Laravel Telescope or Horizon rather than a bundle-provided collector.
- Is m6web/redis-bundle still maintained?
- The signals are weak: roughly 8 stars, no dependents, a single release in 2022, and an origin as an internal Bedrock Streaming (M6Web) package. There is no visible security process, no stated release cadence and effectively one maintainer, which is a poor fit for something sitting in front of every cache and session read. Treat it as reference material rather than a dependency you own.
- What is the best alternative to m6web/redis-bundle for Laravel?
- Use illuminate/redis with either Predis or the phpredis extension, configured through config/database.php with named connections, prefix, serializer, retry and cluster options. Add Horizon if you also need queue observability, and Telescope for command-level debugging. This adds zero new dependencies and is already covered by Laravel's release and security support.
- How do I migrate from m6web/redis-bundle to Laravel's Redis and test the result?
- Start by mapping each configured client to a named connection in config/database.php and replacing injected bundle services with Redis::connection('name') calls. If you genuinely need an unsupported topology, copy only the Predis factory and config classes into app/Redis, bind them behind Illuminate\Contracts\Redis\Factory in a service provider, and pin the exact commit. Test with an in-memory or containerised Redis instance and assert connection selection, prefixing and serialization behaviour in feature tests.