Weave Code
Cache Bundle Laravel Package
openclassrooms/cache-bundle
OpenClassrooms CacheBundle is a Symfony bundle that adds configurable caching services, with cache adapters and pools to store frequently used data, reduce repeated work, and improve application response times.
Symfony2 Bundle for OpenClassrooms Cache
Frequently asked questions about Cache Bundle
- Can I install openclassrooms/cache-bundle in a Laravel application?
- No, not directly. It is a Symfony2 bundle registered through AppKernel with YAML or XML service definitions, so there is no service provider, facade, or config binding that Laravel can consume. Composer resolution will also typically fail because the bundle pins Symfony 2-era constraints and an old PHP range. Treat it as reference code to port, not a dependency to require.
- What Laravel version works with openclassrooms/cache-bundle?
- None officially. The package targets Symfony 2.x and PHP 5.x-era constraints, while Laravel 10 and 11 require PHP 8.1 or newer. Even older Laravel releases have no bundle bootstrapping mechanism for it. If you need the behavior, reimplement it against Illuminate Cache.
- Why does composer require openclassrooms/cache-bundle fail with platform or symfony/framework-bundle conflicts?
- The bundle's constraints pin PHP and Symfony 2 components that conflict with modern illuminate/* requirements. Using --ignore-platform-reqs may force a resolution, but you then risk pulling in ancient, patched-incompatible transitive dependencies. That is not a supported path for a maintained Laravel app.
- What does openclassrooms/cache-bundle actually do?
- It is a Symfony bundle that wires configurable caching services, cache adapters, and pools to store frequently used data and avoid repeated work. In practice it is a thin wrapper around a backend such as Memcached, Redis, or APCu, exposed through the Symfony dependency injection container. The only valuable part is likely its config defaults, key derivation, and eviction or namespacing policy.
- How do I replace openclassrooms/cache-bundle with Laravel's Cache facade?
- Map each bundle service to a Laravel cache store in config/cache.php and call Cache::store('name')->get, put, and forget from your code. If the bundle implemented custom key hashing or namespace isolation, wrap the store in a decorator or a custom Store implementation instead of scattering key prefixes through the app. Then remove the bundle-specific config keys and document the TTL defaults you preserved.
- Is openclassrooms/cache-bundle abandoned or safe for production?
- The repository shows no stars, no dependents, no visible CI, and an organisational vendor that has moved on, so assume it is unmaintained. There is no evidence of a security response process or CVE monitoring. The logic is small, so the practical risk is lifecycle and supply chain rather than behavior. Audit the code and confirm the license before reusing any of it.
- Which Symfony versions does this bundle support, and what should I use instead?
- It was built for Symfony 2.x, roughly the 2012 to 2016 era. For Symfony 5, 6, or 7, use symfony/cache directly, which provides PSR-6 and PSR-16 implementations and is actively maintained. That component almost certainly supersedes whatever abstraction the bundle offered.
- How do I port the bundle's cache adapters and pools to Laravel?
- Start with a source audit: list public methods, config keys, default TTLs, key-derivation rules, and backend selection logic. Write those behaviors as tests covering hit, miss, expiry, namespace isolation, and backend-unavailable failure before writing new code. Then implement them as a CacheServiceProvider plus a custom Store or decorator on top of the Redis or database store Laravel already supports.
- Does openclassrooms/cache-bundle support PSR-6 or PSR-16?
- Almost certainly not. It predates both standards and targets Symfony 2's service-based caching abstraction. Laravel has supported PSR-16 through Illuminate Cache since version 5.8, so a port should target Illuminate\Contracts\Cache\Repository or a PSR-16 adapter rather than the bundle's own contract.
- What license is openclassrooms/cache-bundle released under, and can I reuse the code?
- OpenClassrooms typically publishes under MIT, but the metadata does not confirm it, so check the LICENSE file in the repository before copying anything. If it is MIT, you can reuse the logic with attribution. Regardless of license, prefer rewriting the small amount of caching behavior rather than vendoring an unmaintained Symfony 2 bundle.
Weaver
How can I help you explore Laravel packages today?