- Does ornicar/apc-bundle work with Laravel?
- No. ornicar/apc-bundle is a Symfony bundle that registers APC cache services in Symfony's dependency injection container; it does not provide a Laravel service provider, Cache facade integration, or an Illuminate\Contracts\Cache\Store implementation. Composer may install it in a Laravel project, but you would need a custom wrapper to use it meaningfully.
- Can I install ornicar/apc-bundle with Composer in a Laravel app?
- Composer installation may succeed, but there is no Laravel package discovery or framework integration. The bundle expects Symfony's container and configuration, so installing it alone does not give Laravel a working APC cache driver. Treat installation as insufficient and plan a replacement or adapter instead.
- Is ornicar/apc-bundle compatible with PHP 8 and Laravel 10 or 11?
- There is no assurance of PHP 8.x or Laravel 10/11 support. The package relies on the original APC extension, which was removed in PHP 7+, and the repository is explicitly unmaintained. Modern deployments would need APCu and a custom Laravel cache store, not this bundle.
- What is the difference between APC and APCu for Laravel caching?
- APC originally included both opcode caching and user cache memory, while APCu provides only the user cache API for modern PHP versions. ornicar/apc-bundle targets the legacy APC extension, so APC-versus-APCu confusion is a real integration risk. Laravel would need an APCu-aware store with fallback behavior when the extension is missing.
- Can I use ornicar/apc-bundle as a Laravel cache driver?
- Not directly. Laravel cache drivers implement the Illuminate\Contracts\Cache\Store contract, and this Symfony bundle does not. You could theoretically build an adapter around APCu, but the bundle itself is not the driver and is unmaintained. Prefer Laravel's file, Redis, or database cache drivers for supported behavior.
- What are the production risks of APC or APCu caching in a Laravel deployment?
- APC/APCu is process-local shared memory, so it is a per-host accelerator rather than a distributed cache. Under horizontal scaling, each node has its own cache and invalidation is not centrally coordinated; memory fragmentation can also occur under churn. Do not place sessions, queues, locks, or cross-node coordination on this stack.
- How do I clear the APC cache from the CLI in a Symfony or Laravel app?
- The bundle includes a console command to clear the APC cache, but CLI and FPM often have separate APC/APCu memory, controlled by settings such as apc.enable_cli. Clearing from CLI may not clear the FPM cache unless CLI support is enabled and configured consistently. In Laravel, use framework-native cache clearing for the driver you actually adopt.
- Is ornicar/apc-bundle maintained and safe for new Laravel projects?
- No. The repository is explicitly unmaintained, points to smart-core/accelerator-cache-bundle as a successor, and has zero dependents. The MIT license is clean, but lifecycle, support, and ownership are the blockers. It is not a safe new-adoption choice for Laravel.
- What should I use instead of ornicar/apc-bundle for Laravel caching?
- Use Laravel's native cache drivers such as file, Redis, or database, depending on whether you need single-host speed or shared distributed caching. If you genuinely need local APCu-style caching, use a maintained PSR-6/PSR-16 adapter or a small first-party Laravel store around APCu with graceful fallback. Keep it limited to single-host, non-critical, TTL-bound data.
- How do I migrate a Laravel app away from APC or ornicar/apc-bundle?
- Frame it as replacement rather than integration: inventory keys, TTLs, and read/write patterns, then map them to Laravel's Cache facade with Redis, file, or database drivers. For legacy Symfony apps that require APCu, evaluate smart-core/accelerator-cache-bundle as the maintainer-recommended successor. Publish an ownership plan, deprecation date, and removal milestone before piloting.