Files
nxdns/docs
mokhtar f168247b33
Gates / frontend (push) Successful in 2m23s
Gates / test (push) Successful in 3m15s
Gates / test-aarch64 (push) Successful in 8m38s
Gates / package (push) Successful in 5m0s
Gates / container (push) Successful in 19s
CI / gates (push) Successful in 17m17s
Release / guard (push) Successful in 37s
Gates / frontend (push) Successful in 2m15s
Gates / test (push) Successful in 2m34s
Gates / test-aarch64 (push) Successful in 7m33s
Gates / package (push) Successful in 51s
Gates / container (push) Successful in 10s
Release / gates (push) Successful in 11m14s
Release / publish (push) Successful in 8m35s
cut: build the release with the official zig tarball, skip hidden bundle files; re-pin 0.0.17
The first 0.0.17 cut (run 687) failed verify-pins in CI for two reasons. The asset generator embedded admin/dist/.src-hash, a freshness stamp that CI's artifact copy does not carry; it now skips dotfiles. And the Arch zig package emits different code than the ziglang.org tarball that CI installs, so the cut downloads the pinned tarball (ZIG_TARBALL_SHA256 in gates.yml, the full digest keys the cache) and builds the release with it. flake.nix is re-pinned to the bytes both now produce.

The saturated-primary pool test gates its holders on a semaphore instead of sleeps and releases every spawned holder on the way out, so a loaded runner cannot flake it. The package job uploads the payload before the pin check and runs the check when the version or flake.nix changed against the parent. The verify-a-release recipe clones the tag first and builds with the official zig.
2026-09-08 23:57:07 +02:00
..

nxdns documentation

The pages are split by what you are trying to do, following Diátaxis. Each page serves one of four purposes, and knowing which one you want is the fastest way to the right page.

Mode For Read it when
Tutorial Someone who has never run nxdns You want to learn what it does by making it work once
How-to guides An operator with a job to do You know what you want and need the steps
Reference Anyone who needs an exact answer You want a field, a flag, a route or an exit code
Explanation Anyone deciding or debugging You want to know why it works the way it does

Tutorial

A lesson, not a procedure: one path with one outcome, on a scratch directory you can delete afterwards.

  • tutorial/first-run.md — build nxdns, resolve a name, block a domain from a real blocklist, open the web interface, stop cleanly.

How-to guides

Steps for a goal you already have. They assume you know what nxdns is.

Reference

Descriptions of what is there. No procedures, no advice.

Explanation

Background. Nothing here is needed to operate nxdns; it is here so the decisions are inspectable.

Scope and per-milestone contracts live outside this directory, in ../PLAN.md and ../specs/.