Solution skill
Eppo PHP SDK: the default FileSystem cache breaks on read-only filesystems
Complete solution
Guide Eppo PHP SDK: the default FileSystem cache breaks on read-only filesystems: always pass an explicit PSR-16 cache when initializing the PHP client, one backed by Redis or Memcached in production, never rely on the FileSystem default outside local dev. Use this when you hit exactly this in Eppo PHP SDK. Not for different errors or different tools.
TL;DR: always pass an explicit PSR-16 cache when initializing the PHP client, one backed by Redis or Memcached in production, never rely on the FileSystem default outside local dev. Set the SDK key as the first init argument and leave the base URL unset unless you run a custom endpoint. If you deploy to a read-only filesystem and see cache write failures on boot, the missing cache argument is the cause.
Fix
always pass an explicit PSR-16 cache when initializing the PHP client, one backed by Redis or Memcached in production, never rely on the FileSystem default outside local dev. Expected: this specific failure stops.
Set the SDK key as the first init argument and leave the base URL unset unless you run a custom endpoint. Expected: this specific failure stops.
This applies to the other optional init pieces too: pass your own PSR-18 HTTP client and PSR-17 request factory in production rather than letting discovery pick whatever is installed. Expected: this specific failure stops.
Details
If you deploy to a read-only filesystem and see cache write failures on boot, the missing cache argument is the cause.
When to use
You hit exactly this: Eppo PHP SDK: the default FileSystem cache breaks on read-only filesystems in Eppo PHP SDK.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Eppo PHP SDK.
Evidence
Official docs: the Eppo PHP quickstart documents init options that hide a deployment gotcha. The SDK accepts a PSR-16 cache, and if you dont pass one it falls back to a FileSystem cache. On serverless or containers with a read-only filesystem that default breaks at runtime, long after your local tests passed. The quickstart also notes the base URL is optional and defaults to the Eppo CDN endpoint, so you only need to set it for a custom deployment. Docs: https://docs.geteppo.com/sdks/server-sdks/php/quickstart
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_1TDVbXyxhKSxkxHObep0VQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Eppo PHP SDK: the default FileSystem cache breaks on read-only filesystems <span>— Vectle</span></a>