- What is m6web/apcu-bundle used for?
- It is a lightweight Symfony bundle for integrating APCu into a Symfony application. It exposes APCu cache operations as a Symfony service and provides a console command to clear the APCu cache. It is aimed at projects that use APCu for in-memory caching and need simple operational tooling for deployment and maintenance.
- Is m6web/apcu-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The package name and repository describe Symfony dependency injection and console integration. If you are evaluating it for Laravel, confirm that the service and command integration fit your framework before adopting it.
- How do I install m6web/apcu-bundle?
- Install it with Composer using the package name m6web/apcu-bundle. You will also need the APCu PHP extension enabled in the PHP runtime where the bundle is used. Register the bundle in your Symfony application according to the version's documentation, then verify the service and console command are available.
- How do I clear APCu cache from the Symfony console?
- The bundle provides a console command specifically for clearing the APCu cache. Run the command from your Symfony project after enabling the bundle and confirming the command is registered. Use it as part of deployment or maintenance scripts where APCu cache invalidation is required.
- How do I use the APCu cache service in Symfony?
- The bundle exposes APCu cache operations through a Symfony service. Inject that service into your own services or controllers through Symfony's dependency injection container. This keeps APCu calls behind a service instead of scattering apcu_* functions throughout your application.
- Which Symfony and PHP versions does m6web/apcu-bundle support?
- The provided context does not list a Symfony or PHP version matrix. Check the package's composer.json constraints and the release notes for the version you plan to use. Treat a major version bump, such as v3.0.0, as a possible change to supported Symfony and PHP versions until confirmed.
- What changed in m6web/apcu-bundle v3.0.0?
- The release note for v3.0.0 only says to see issue #16, so the change details are not available in the provided context. Review issue #16, the changelog, and the diff before upgrading. A major version bump should be assumed to carry possible breaking changes, deprecations, or minimum-version changes.
- What are the requirements for using APCu with this bundle?
- APCu must be enabled in the PHP environment where the bundle runs. Because APCu is an in-memory cache tied to the PHP process and SAPI, confirm whether the console command clears the cache for your web runtime as expected. Test in an environment that matches your production PHP-FPM or web server setup.
- How should I test m6web/apcu-bundle before deploying?
- Install it in an isolated branch or staging environment with APCu enabled and confirm the service is injectable and the console command is registered. Run your Symfony test suite and a smoke test that exercises cache reads, writes, and clearing. Then deploy to staging with representative data and keep a rollback path before production rollout.
- What are alternatives to m6web/apcu-bundle?
- Symfony's own cache component with an APCu adapter is a common alternative for in-memory caching. You can also write a small application service around apcu_* functions if you only need a few operations. Compare maintenance status, Symfony version support, and whether you need a console command before choosing.