- Is fm/cache-bundle compatible with Laravel?
- No, fm/cache-bundle is not a Laravel package. It is a Symfony2 bundle for cache pools and Doctrine-oriented caching, and its wiring does not align with Laravel's service container or cache manager. Treat it as a design reference rather than a dependency in a Laravel application.
- How do I install fm/cache-bundle in a Laravel application?
- There is no supported installation path for fm/cache-bundle in a modern Laravel app. Composer may resolve the package in an isolated legacy Symfony2 project, but dropping it into Laravel would require custom integration code and compatibility work. If you only need caching in Laravel, use the built-in Cache facade and Laravel-supported drivers instead.
- What Laravel and PHP versions does fm/cache-bundle support?
- The package was last released in 2013 and targets Symfony2-era PHP and Doctrine assumptions. It does not declare support for modern Laravel versions or PHP 8.x, so compatibility with current Laravel is unknown and very likely to fail without a port. Do not assume Laravel 9, 10, 11, or 12 support.
- Does fm/cache-bundle work with Eloquent or Doctrine ORM?
- fm/cache-bundle is associated with entity and ORM caching concepts, likely Doctrine, not Eloquent. Laravel's Eloquent stack does not use Doctrine's identity map or second-level cache semantics, so the bundle's behavior cannot be mapped directly. For Eloquent, use Laravel Cache, query-result caching, or model observers with explicit invalidation instead.
- Can fm/cache-bundle replace Laravel Cache for Redis or Memcached?
- It should not replace Laravel Cache in a standard Laravel application. Laravel's Cache facade already supports Redis, Memcached, database, file, and other stores with consistent APIs and configuration. The bundle's pool wiring is Symfony2-specific and would add legacy integration risk rather than simplify Redis or Memcached usage.
- How do I configure multiple cache pools with fm/cache-bundle?
- Configuration would follow Symfony2 bundle conventions, such as service container definitions for named cache pools. In Laravel, you would need to translate those definitions into Laravel services or config/cache.php entries, and there is no documented Laravel integration. This makes the package a poor choice for configuring multiple pools in a Laravel project.
- Does fm/cache-bundle support PSR-6 and PSR-16 cache adapters?
- The package overview mentions PSR-6 and PSR-16 compatible adapters, but the 2013 release predates current PSR standards and modern cache implementations. Verify any PSR claims in an isolated legacy environment before relying on them. In Laravel, prefer PSR-compatible packages that are actively maintained and tested against current PHP versions.
- How should I test fm/cache-bundle before using it in a Laravel project?
- Testing it in Laravel would require a compatibility spike first, because the bundle is not designed for Laravel's container or cache manager. You would need to isolate Symfony2/Doctrine dependencies, verify PHP 8.x behavior, and test cache-key handling and invalidation manually. That effort is usually greater than prototyping the same caching with Laravel Cache.
- Is fm/cache-bundle safe for production and actively maintained?
- No, fm/cache-bundle is archived, last released in 2013, and has no upstream maintenance or community support. Using it in production would make your team responsible for security fixes, PHP compatibility, and integration code. For Laravel production caching, choose maintained Laravel-native drivers or actively supported packages.
- What are Laravel-native alternatives or migration options to fm/cache-bundle?
- Start by documenting the cache semantics you need, such as entity caching, query caching, TTLs, and invalidation rules. Then implement them with Laravel Cache, repository decorators, Eloquent observers, or a maintained Doctrine cache package if Doctrine is mandatory. Do not plan a direct migration from fm/cache-bundle into production Laravel code.