Server configuration

The server needs no configuration file — everything is a command-line flag, and every flag has a sensible default:

./yocache --addr :6768 --quota 500GiB --evict lru

Every flag can also be set via a YOCACHE_<FLAG> environment variable instead — handy for Docker and systemd, where env vars are the natural way to configure a container or unit. A CLI flag always wins over its env var, which wins over the compiled-in default.

Flag	Env var	Default	What it does
--addr	YOCACHE_ADDR	:6768	Address the HTTP server listens on.
--hashequiv-addr	YOCACHE_HASHEQUIV_ADDR	:6767	Address a second, dedicated raw-TCP hash-equivalence listener binds to — for pre-Scarthgap bitbake (Dunfell and earlier), whose hash-equivalence client has no ws:// support. On by default; set to "" to disable it.
--data-dir	YOCACHE_DATA_DIR	var	Root directory for all persistent state: the operational database (yocache.db), the blob stores (downloads/, sstate/), and the audit logs (yocache.ledger.jsonl, yocache.access.jsonl).
--quota	YOCACHE_QUOTA	0 (unlimited)	Total storage cap for all cached artifacts, e.g. 500GiB. When full, eviction (below) frees space on demand.
--evict	YOCACHE_EVICT	(none)	Eviction policy used when the quota is reached: lru removes the least-recently-used artifacts first, lru-sstate restricts that to sstate objects. Repeat the flag (or comma-separate the env var, e.g. YOCACHE_EVICT=lru,lru-sstate) to chain policies in order. An sstate task’s archive and its .siginfo/.sig sidecars are always evicted together, and evicting one also drops its hash-equivalence entry — no separate GC pass needed, unlike bitbake’s own hash-equivalence server.
--block-recipe	YOCACHE_BLOCK_RECIPE	(none)	Recipe name whose artifacts the cache should refuse to store or serve — an escape hatch for a recipe known to produce broken sstate. Repeat the flag (or comma-separate the env var) to block more. Never affects source downloads.
--build-stats-ttl	YOCACHE_BUILD_STATS_TTL	720h (30 days)	How long to retain per-build download statistics.

Both logs are plain JSONL — one JSON object per line — so they’re easy to inspect with jq or load into any analytics tool.

Health and stats endpoints

GET /healthz answers as soon as the server is up, and GET /api/stats returns a JSON summary of what’s in the cache — file counts and sizes for downloads and sstate. Handy for dashboards and for confirming the cache is actually filling up.

For the build-side knobs, see Client configuration.