entries export and entries import round-trip a .env file key by key, not as one opaque blob - but the real fix for a growing team is that config lives in one place and every change reaches everyone immediately.
61MiB idle and a container that starts instantly - and no profiler on the binary we ship, no embedded database replicas, and no building it on the machine we develop on. The whole invoice.
The harness warmed the heap before measuring it, Docker reported page cache as our memory, port forwarding made one number six times worse, and the build system said a broken project compiled.
We rewrote the data layer, dropped Microsoft.Data.Sqlite, went UTF-8, and streamed SQLite straight into the socket. Most of it failed. Here is what we measured and why we stopped.