Writing · infrastructure
6 posts filed under infrastructure, newest first.
Every provider publishes a trust page nobody can check. Ours is generated at build time from artifacts the hosts sign themselves — and the build refuses to render numbers no host put its key behind.
Three months, four NixOS hosts, 1,221 commits, and a CI pipeline that did not exist in August — plus the week the commit log changed hands for good.
CPUWeight and IOWeight are shares of contention, not ceilings: a weight of 10 beside 100 gets a tenth of whatever is contended, and nothing when idle.
VictoriaLogs keeps every line it is given, so a retrying agent or a restart loop doubles your history — de-duplication is the caller's job, not the store's.
On NixOS a config change edits a file, not a running process. Without restartTriggers the deploy is green and the old configuration stays resident in memory.
Fitting a 27B model on one 24GB card is two arithmetic unknowns - weight memory at your quantisation and KV cache at your context - and a curve, not a number.