Weave Code
Apc Bundle Laravel Package
orkestra/apc-bundle
A small bundle that adds APC/APCu cache support to Orkestra applications, wiring cache services and configuration so PHP's shared memory cache can be used through the framework's standard cache abstractions. Useful for fast local caching without external services.
APC Cache Bundle for Symfony 2 PHP Framework
Frequently asked questions about Apc Bundle
- Is orkestra/apc-bundle a Laravel package?
- No. It is a Symfony 2 bundle that registers through AppKernel::registerBundles() and Symfony DependencyInjection extensions. It ships no Laravel service provider, no extra.laravel auto-discovery entry, and no config/cache.php integration. Treat it as a foreign component in a Laravel codebase.
- Can I install orkestra/apc-bundle in a Laravel application with Composer?
- Composer may resolve and download it, but installing it does not wire anything into Laravel. There is no service provider to register the cache service with Laravel's container or Cache facade. Without that wiring the package does nothing in a Laravel app, so installation alone provides no caching capability.
- Does orkestra/apc-bundle support Laravel 10 or Laravel 11?
- No. Every currently supported Laravel release requires PHP 8.x, while this bundle targets the legacy APC extension on PHP 5.x and Symfony 2 conventions. APC does not build on PHP 7 or 8, so the runtime requirement alone rules it out. There is no supported configuration that makes it work on modern Laravel.
- Will APC or APCu run on PHP 8, and does this bundle support it?
- APCu supports PHP 7 and 8, but the older APC extension does not build on PHP 7 or later and has been effectively unmaintained since around 2012. This bundle is written against the legacy APC API and Symfony 2 service wiring, not modern APCu. Even where APCu is available, the bundle's adapter logic is not the code you would use.
- How do I configure cache namespaces and TTLs in orkestra/apc-bundle?
- Configuration is done through the Symfony bundle's DependencyInjection extension in Symfony config files, not through Laravel's config/cache.php. There is no Laravel-facing configuration surface, environment variable mapping, or publishable config file. In a Laravel project you would have to write that configuration layer yourself.
- What is the difference between APC, APCu, and OPcache for caching?
- OPcache accelerates PHP by caching compiled opcode and is a runtime configuration concern, not a Composer package. APCu provides user-land shared-memory caching on a single host, while the older APC combined both roles and is obsolete. Laravel's native cache drivers cover user-land caching without needing this bundle.
- What are the best alternatives to orkestra/apc-bundle for Laravel caching?
- Use Laravel's built-in cache drivers for Redis, Memcached, database, file, and array, all configured through config/cache.php and the Cache facade. Enable OPcache in PHP for opcode acceleration and APCu only if you need per-host user cache. If you want a framework-agnostic abstraction, symfony/cache is maintained and PSR-6/PSR-16 compliant.
- Is orkestra/apc-bundle maintained and safe for production?
- No. It has minimal community traction, no dependents, and no visible maintenance cadence, and it depends on Symfony 2, which left security support in 2019. APC itself is unmaintained and PHP 5.x is unsupported. Adopting it means accepting unpatched code on the request hot path with a single-maintainer bus factor.
- How do I migrate from orkestra/apc-bundle to Laravel's cache system?
- Replace the bundle's cache service with Laravel's Cache facade and a driver defined in config/cache.php, such as Redis, Memcached, file, or array. If you specifically need single-host shared memory, use the APCu extension directly behind a small custom cache driver rather than this bundle. For multi-node deployments, choose Redis. Treat any remaining Symfony 2 runtime as frozen and fund migration off PHP 5.x.
- Can I use orkestra/apc-bundle with Laravel Octane or across multiple servers?
- No. APC and APCu are per-host shared-memory caches, so they are not shared across nodes and are a poor fit for horizontally scaled or containerized deployments. Laravel Octane also expects cache services wired through Laravel's container and cache contracts, which this bundle does not provide. Use Redis or Memcached for cross-node caching in Laravel.
Weaver
How can I help you explore Laravel packages today?