- Is electivegroup/cache-bundle compatible with Laravel?
- No, it is a Symfony bundle rather than a Laravel package. It relies on Symfony bundle registration, YAML route imports, and YAML service imports, which do not map to Laravel's service provider discovery, route files, or config repository. Direct adoption would require pulling in Symfony components and manually wiring services, which creates version-conflict risk and leaves its routes outside Laravel middleware, auth, and CSRF handling.
- How do I install electivegroup/cache-bundle in a Laravel app?
- You can install it with Composer, but it will not auto-register or function in a standard Laravel application. The README only documents Symfony installation: importing the bundle's routes.yaml and services.yaml. For Laravel, the realistic path is to treat it as a reference design and build a Laravel-native cache invalidation service instead.
- What does the CACHE_SUBSCRIPTIONS environment variable do in electivegroup/cache-bundle?
- The bundle reads CACHE_SUBSCRIPTIONS from your env file as a comma-separated list of cache invalidation channels, such as ACL or user update events. The idea is to make cache invalidation environment-specific. Laravel's .env convention is compatible with the variable itself, but the Symfony consumer that reads it is not portable to Laravel without a rewrite.
- Which Symfony and PHP versions does electivegroup/cache-bundle support?
- The README does not state supported Symfony or PHP versions, and there is no visible compatibility matrix. The last release was 2024-02-23, with no CI or test coverage shown. You should review the source and composer constraints before making any dependency decision.
- How does cache invalidation work in electivegroup/cache-bundle?
- The bundle adds cache routes and services through config imports and uses CACHE_SUBSCRIPTIONS to define invalidation channels in the environment. The README does not describe the transport behind subscriptions, whether that is Redis pub/sub, a message broker, or HTTP callbacks. It also does not document the publisher side or the channel naming contract, so source review is required.
- Are the electivegroup/cache-bundle routes authenticated or protected?
- The README does not describe authentication or authorization for the routes the bundle adds. That is a significant production concern because cache invalidation endpoints can cause stale data or load spikes if exposed incorrectly. You must inspect the source before exposing any routes in a real application.
- Is electivegroup/cache-bundle maintained and safe for production?
- The package has 0 stars, 0 dependents, and no evidence of production adoption. The README stops at installation, and there is no visible CI, test coverage, or compatibility matrix. Cache invalidation is a silent-failure domain, so assume fork-and-own risk and plan for source review and tests before production use.
- How would I build Laravel-native cache invalidation inspired by this bundle?
- A Laravel-native equivalent would use a service provider, a config/cache-bundle.php file, and a Redis pub/sub or queue-backed subscription worker. Invalidation listeners would use Laravel's cache and event systems, with channel names defined in .env just like CACHE_SUBSCRIPTIONS. This is typically 150 to 300 lines plus tests and is the recommended path over porting the Symfony bundle.
- Does electivegroup/cache-bundle work with Laravel's cache and event systems?
- No, it is built around Symfony dependency injection, routing, and config loading rather than Laravel's cache repository and event dispatcher. Laravel shares some Symfony components such as HttpFoundation and Console, but not the full FrameworkBundle and bundle registration model this package expects. Using it would mean adopting a Symfony execution model inside Laravel, which is an architectural mismatch.
- What alternatives exist for Laravel cache invalidation if this bundle is Symfony-only?
- There is no known Laravel-compatible fork of electivegroup/cache-bundle in the provided context. The practical alternative is to implement the subscription-channel pattern natively in Laravel using env-driven channel names, a queue or Redis pub/sub worker, and Laravel cache and event listeners. Treat the bundle as a design reference rather than a drop-in dependency.