- How do I install jord-jd/do-file-cache-psr-6 in a Laravel app?
- Install it with composer require jord-jd/do-file-cache-psr-6. Then bind Psr\Cache\CacheItemPoolInterface in your container to an instance that wraps the DO File Cache pool. Laravel has no native PSR-6 cache slot, so you consume the pool directly in new code rather than through the Cache facade.
- Can I use this package as a Laravel cache driver in config/cache.php?
- No. Laravel's Cache facade is built on Illuminate\Contracts\Cache\Store, not PSR-6, and there is no psr6 driver you can configure. You can bind CacheItemPoolInterface and use PSR-6 directly, or write a bridge Store implementation to expose the pool via Cache::store(). That bridge is your code, not part of this package.
- Does jord-jd/do-file-cache-psr-6 work with Laravel 10, 11, or 12?
- There is no official recent Laravel support signal. The package has no trustworthy current CI, and its psr/cache version constraint may not satisfy modern dependency graphs, so run composer why-not psr/cache first. It is a thin adapter, so patching is likely small, but you are the integration test.
- Is this a DigitalOcean package? Does it need DO API keys or Spaces?
- No. Despite the DO name, this is not a DigitalOcean product and does not use Spaces, S3, cloud credentials, or multi-region replication. It is a PSR-6 adapter over jord-jd/do-file-cache, which is a local filesystem cache. Earlier notes mentioning DO API keys and filesystem replication are incorrect.
- What cache features are missing, such as tags, locks, or atomic increments?
- PSR-6 itself has no tag, lock, or atomic increment semantics, and this adapter does not add them. You get basic PSR-6 item operations backed by serialized files on local disk. If your code relies on Cache::tags(), Cache::lock(), or atomic counters, it cannot move to this pool unchanged.
- Can I use this package on multiple app servers or in a horizontally scaled deployment?
- No, not as a shared cache. A filesystem cache is per-host, so each server gets an independent cache with divergent reads and invalidation that only clears the host that served the request. Shared NFS is not a safe workaround because file locking and failure modes are unreliable, so use this only for single-host or per-node caching.
- What license does jord-jd/do-file-cache-psr-6 use, and is LGPL okay for commercial Laravel apps?
- The package is LGPL-3.0. Many organizations allow LGPL for unmodified Composer-installed dependencies, but some ban it by default, so legal review is a gate before adoption. Run that policy check in parallel with any technical spike rather than after it.
- How should I test this PSR-6 adapter before using it in production?
- Install it in a branch and run composer why-not psr/cache to see the resolved psr/cache version. Write a small integration test that binds CacheItemPoolInterface and exercises get, set, delete, and expiration against a temporary directory. Verify behavior on your target PHP version because the README's Travis CI badge is not a reliable signal. Also confirm that your deployment model is single-host or per-node.
- Is jord-jd/do-file-cache-psr-6 maintained? What is the bus factor?
- It has one maintainer, roughly 8 stars, zero dependents, and recent releases have been a namespace move and a docs-only badge fix. Treat it as unmaintained by default: if it breaks, you fork it. That is acceptable for a small adapter you can read quickly, but not for critical shared caching.
- What is the difference between this package and Laravel's file cache driver or symfony/cache?
- Laravel's file driver is a full Illuminate cache Store with Cache facade integration, while this package is only a PSR-6 CacheItemPoolInterface adapter over DO File Cache. symfony/cache provides PSR-6 and PSR-16 adapters with broader maintenance and feature coverage. Choose this package only if you already have a concrete reason to use DO File Cache and accept the bridge and single-host limitations.