Release nitr v0.9.0 · bitcav/nitr

nitr key, nitr passwd, and nitr qr now fail when nitr.db is absent
instead of silently creating one. They previously provisioned a fresh
nitr.db and config.ini (with the default 123456 user) on every
invocation, so running them in a directory where the server had never been
started minted a second, divergent credential store. They now exit with a
clear error naming the working directory and pointing at the server, which
remains the only thing that creates the database. nitr version likewise no
longer leaves nitr.db and config.ini behind as a side effect — it and
the other informational commands (-h, help, unknown commands) keep the
working directory clean. If you scripted key/passwd/qr against an
empty directory expecting them to provision, start the server there first. (cd09fb1, 836a422)
The web panel no longer honours a remember cookie. Login and the auth
middleware granted access on Cookie: remember=1, a value the server never
set, so anyone who could reach the panel could authenticate by sending it.
Authentication is now session-only; no legitimate session is affected. See
Security below for the full rationale. (4db6420)

Prometheus /metrics endpoint, emitting the standard exposition format
behind the same x-api-key header as the JSON API. Exposed series are
nitr_cpu_seconds_total{cpu,mode} (a counter; derive utilisation with
rate() in PromQL), nitr_ram_{total,free,used}_bytes, and
nitr_disk_{free,size,used}_bytes{mountpoint} — all nitr_-prefixed,
snake_case, base units. Per-interface bandwidth is deliberately not exposed:
bandwidth.Info sleeps 1s to derive a netdev delta, which would cause
scrape timeouts; it will land with a background sampler. The README
documents a working scrape_config that passes the key via
http_headers.secrets. (ac9cdb8)
The test suite now runs on Windows (windows-2025) alongside Linux, with a
per-leg smoke test that builds the real binary and runs nitr version on
each OS and asserts a sane version string. This is the guard that would have
caught the v0.8.0 init()-panic class of bug, where every compiled binary
died before main while go test stayed green. (7584cd2, dc3c547, 8c1c0cf)

The README was overhauled: a 30-second quick start, a platform badge, a
rewritten intro, and a reorganised table of contents. It now also documents
the CLI database precondition (key/passwd/qr operate on the database
in the current working directory and require the server to have run there)
and states which platforms CI actually verifies on each push. (b8fc37d, d65060a)
The README network table was corrected: /network returns an array of
objects ([{"ip": ...}]), not an array of strings as previously documented.
A JSON example was added, since the nested shape is not expressible in the
flat key/type table. (34235f2)
The API field reference moved out of README.md into a new docs/API.md.
Those 16 sections previously lived inside collapsed <details> blocks, so
every "JSON Data" link in the endpoint table scrolled to hidden content; the
table now links across to docs/API.md, where the targets are ordinary
visible headings. No field-reference content changed. (faab898)
The README quick start no longer opens with sudo and states plainly that
Nitr does not need root to run. Privilege notes are now per-field rather than
per-endpoint: only serial/uuid on the DMI endpoints require root
(verified against the kernel's drivers/firmware/dmi-id.c), while /memory
requires it wholesale. (faab898)
The README endpoint table now documents GET /api/v1/, which was routed but
previously undocumented. (faab898)

nitr version printed no trailing newline, so its output ran into the next
shell prompt. (1b7549b)
program.Stop — the service-manager shutdown hook — was an empty stub that
returned nil without stopping anything, so stopping the Nitr service left
the HTTP server running. It now calls app.Shutdown(). (c1389a0)
The /status websocket reader ran on a hijacked-connection goroutine that
fiber's recover middleware does not cover, so a panic while handling an
inbound message crashed the whole process. It now recovers explicitly, logs
the panic, and lets the library release the connection. (f1a2af8)
A startup failure opening nitr.log (when save_logs is on) called
log.Fatalf from the background goroutine spawned by the service manager,
os.Exit-ing the process from outside main's error-reporting path. The
error is now returned through main and reported cleanly. (76f329f)
CLI argument routing through the internal dispatch path now forwards its
arguments to the subcommand parser instead of falling back to os.Args.
The two were equivalent for normal nitr <command> use, so no production
behaviour changed, but dispatch now routes as its signature promised and is
testable without parsing the test binary's own flags. (20eb9b9)
The password-change success message read "Password changed succesfully!"
("succesfully" → "successfully"). (a2182c7)

Navigation Menu