SrvOS was oudated and still using ther zstd nginx settings which are no longer recommended to use. This made eval fail with an assertion. Change-Id: If5edf99247e0500f6d23325a4f2dd34cb31d8252 Reviewed-on: https://cl.snix.dev/c/snix/+/30664 Autosubmit: Ilan Joselevich <personal@ilanjoselevich.com> Tested-by: besadii Reviewed-by: Florian Klink <flokli@flokli.de> |
||
|---|---|---|
| .. | ||
| default.nix | ||
| disko.nix | ||
| monitoring.nix | ||
| nar-bridge-module.nix | ||
| nar-bridge.nix | ||
| OWNERS | ||
| README.md | ||
nixos-snix-cache
This is a fetch-through mirror of cache.nixos.org, hosted by NumTide.
The current machine is a SX65 Hetzner dedicated server with 4x22TB SATA disks, and 2x1TB NVMe disks.
The goals of this machine:
- Exercise snix-store and nar-bridge code
- Collect usage metrics (see Grafana)
- Identify bottlenecks in the current implementations and fix them
- Replace cache.nixos.org?
You can configure this as a Nix substitutor on your systems like this:
nix.settings.substituters = [
"https://nixos.snix.store"
];
For store paths it hasn't already seen yet, it'll internally ingest its contents into snix-castore (deduplicating in doing so).
Requests for NARs will dynamically reassemble the NAR representation on demand.
Metadata and signatures are preserved (which is why you don't need to add additional trusted keys). We need to produce the same data bit by bit, else the signature check in your Nix/Lix client would fail.
Be however aware that there's zero availability guarantees. We will frequently redeploy this box, and it might become unavailable without prior notice.
Snix currently doesn't have garbage collection. If we run out of disk space, we might either move things to a bigger box or delete everything on it so far.
As it's only a cache, it should however re-ingest things again.