- Is mmoreram/cache-flush-bundle a Laravel package?
- No. mmoreram/cache-flush-bundle is a Symfony bundle that integrates through Symfony's Bundle class, DI container compiler passes, and Console commands registered by framework-bundle. Laravel uses service providers, facades, and Artisan commands instead, and this repository contains no adapter layer. There is also no separate Laravel bridge elsewhere; it has zero dependents.
- Can I install mmoreram/cache-flush-bundle in a Laravel application?
- Technically Composer might resolve some subset, but it is not supported by Laravel or the package. You would need to install symfony/framework-bundle and bootstrap a second DI container inside Laravel, which is a heavy, unsupported pattern. The practical answer is no for a Laravel application.
- What does mmoreram/cache-flush-bundle actually do?
- It provides a small Symfony service and console command for flushing the application cache. The goal is to let controllers, deployment scripts, or admin tooling trigger cache invalidation without duplicating cache-clearing logic. It wraps Symfony's cache-clearing mechanisms and keeps that logic centralized and reusable within a Symfony application.
- Does Laravel already have commands to flush the application cache?
- Yes. Laravel ships cache:clear, config:clear, route:clear, view:clear, event:clear, and the aggregate optimize:clear. These cover standard application cache, config, routes, views, and events with no extra dependency. If you need opcache, CDN edge, or Redis tag namespaces, you still need custom code, but this bundle does not provide that either.
- Is mmoreram/cache-flush-bundle abandoned or safe for production?
- No. The last release was 2016-12-28, roughly nine years ago, which predates Symfony 4, Symfony Flex, PHP 7.4+, and PHP 8.x. It has one star and zero dependents, so there is no production validation in the ecosystem. The upstream maintainer has deprecated a large portfolio of packages, and there is no security response path.
- Which Symfony and PHP versions does mmoreram/cache-flush-bundle support?
- Its Composer constraints are pinned to the Symfony 2.x and 3.x era. It should be assumed incompatible with PHP 8.2 and 8.3 type semantics, and therefore with modern Laravel 10, 11, and 12 applications. You would need an actual install spike to prove otherwise.
- What Composer conflicts should I expect if I add this bundle to Laravel?
- Adding it pulls symfony/framework-bundle alongside illuminate/*, creating two container paradigms and conflicting kernel bootstrapping. Expect Composer resolution conflicts on symfony/console, symfony/http-kernel, and psr/* constraints. Every future Laravel upgrade becomes a fight with those constraints.
- How do I flush caches across multiple Laravel servers or hosts?
- This bundle does not solve cross-host coordination; it only registers a Symfony console command and service. Flushing across N hosts is a deployment orchestration problem, often handled with queue jobs, Redis tag namespaces, CDN purge APIs, or running native Laravel commands on each host. You would still need custom code for those layers.
- What is the best Laravel alternative to this Symfony cache flush bundle?
- Use Laravel's native Artisan commands first: cache:clear, config:clear, route:clear, view:clear, event:clear, and optimize:clear. If something is genuinely missing, write a small Artisan command plus a service provider, realistically 50 to 150 lines including config. If a Symfony service in your estate truly needs this behavior, evaluate a modern maintained Symfony alternative separately rather than forcing this 2016 bundle into Laravel.
- Do I need an adapter or bridge to use Symfony bundles in Laravel?
- No supported adapter or bridge exists. Laravel has no bundle concept; it uses service providers, facades, and Artisan commands, and this repository has no Laravel integration layer. Installing symfony/framework-bundle inside Laravel is a heavy, unsupported pattern, so treat this package as a pattern reference rather than a dependency.