Weave Code
App Cache Bundle Laravel Package
php-solution/app-cache-bundle
php-solution/app-cache-bundle provides application-level caching for PHP projects, with configurable cache storage and simple integration to speed up repeated work and reduce load.
Symfony bundle for using Redis as main cache on app.
Frequently asked questions about App Cache Bundle
- Is php-solution/app-cache-bundle compatible with Laravel?
- No. The package is a Symfony bundle and depends on Symfony's Bundle class, DependencyInjection extension, and kernel-level registration in config/bundles.php. Laravel's service-provider model has no equivalent boot path, so Composer may download the code but nothing in bootstrap/app.php or the container will ever boot it. Treat it as incompatible with a standard Laravel application.
- Can I use this Symfony cache bundle in Laravel through a custom service provider?
- Only by reimplementing its caching logic inside a Laravel service provider or by bridging Symfony conventions into your Laravel codebase. That adds maintenance and cognitive load with no demonstrated payoff, especially since the package has no Laravel integration layer. For Laravel caching, use Illuminate\Support\Facades\Cache and native cache repositories instead.
- What does php-solution/app-cache-bundle actually do?
- It adds a configurable application-level cache layer to Symfony projects and wires PSR-6 or PSR-16 adapters into the container. It supports declarative cache pool configuration in YAML, integration with Symfony cache contracts and tagged services, pluggable adapters, and cache warmup and clear commands for deployment workflows.
- Which cache backends does app-cache-bundle support?
- The package description mentions filesystem, Redis, and array adapters selected through a single setting. However, the provided metadata does not include a compatibility matrix or detailed backend requirements. You should inspect the source and composer.json before assuming a specific backend or PSR interface is supported.
- How do I install php-solution/app-cache-bundle in a Symfony project?
- The expected Symfony path is to require the package with Composer, register the bundle in config/bundles.php, and configure cache pools in YAML. The repository has very little external validation, so verify the service names, configuration keys, and supported Symfony versions directly from source. Do not assume a stable install path from the README alone.
- Does app-cache-bundle support PSR-6 and PSR-16 cache interfaces?
- The overview says it wires PSR-6 and PSR-16 adapters into the container, which aligns with Symfony cache contracts. It is not clear from the provided metadata which interface each pool exposes or how adapters are selected per environment. Read the bundle extension and service definitions to confirm the exact behavior.
- Is php-solution/app-cache-bundle production-ready?
- There is no strong production signal: the repository has about 2 stars, 0 dependents, and no documented CI, changelog, or issue history in the provided assessment. An application-level cache layer is also where framework upgrades and unknown invalidation semantics can cause incidents. Treat it as a reference implementation or spike candidate, not a committed dependency.
- What Laravel caching alternative should I use instead of this bundle?
- Use Laravel's native caching stack: the Cache facade, cache repositories, tagged caches, configured drivers, and response-cache middleware where appropriate. Those APIs are maintained with the framework and avoid the need to bridge a Symfony bundle into Laravel. A small custom service provider can cover most application-level pooling needs.
- Does app-cache-bundle have tests, CI, or a changelog?
- The provided technical assessment does not identify a test suite, CI pipeline, changelog, or semantic versioning discipline. With zero dependents and no issue history, there is also no ecosystem safety net to surface edge cases. Ask the maintainer or inspect the repository before relying on it for deployment workflows.
- What license does php-solution/app-cache-bundle use, and who maintains it?
- The license and maintainer details are not included in the provided metadata. You should check the repository's LICENSE file, composer.json, and release history before procurement or dependency-scanning review. The maintainer bus factor is a real concern given the low star count and lack of downstream consumers.
Weaver
How can I help you explore Laravel packages today?