Troubleshoot: dnf's 48h metadata default hides a new release
3.2.0 and 2.2.7 are released, not pending
Timers, and correct the panel's auth story A page for one-shot timers (why they are not programs, what 'fired' does and does not prove), the /api/timers endpoints, and the two new settings. Also fixes something this wiki got wrong: 'The web panel' said the browser's credential was an Ed25519 key pair. That was not true of 3.1.0 -- the panel was the last client still on the bearer token, which is exactly why AC_MIN_AUTH_VERSION=2 used to lock the panel out. It is true from the next release, and the page now says which is which.
Add a version history, v1.0.0 to 3.1.0 What each release actually gave you, reconstructed from the release notes, the tags and the git history rather than from memory -- including the three gaps that look like mistakes and are not: there was never a 2.0 or 2.1, 2.7.0 was the number Ed25519 signing was developed under before it shipped inside 3.0.0, and 3.0.2 was followed by 3.0.5. Also records what has landed since 3.1.0 without a version of its own yet: the OPNsense plugin, the five rebuilt container images, and this wiki.
The documentation, moved out of the repo and organised 24 pages behind a sectioned sidebar. The README was 2,000 words and docs/ another 25,000, so the front door read like a manual and the manual had no structure. Start here Home · Compared to NetHome Plus · First run and pairing Install packages · containers · Windows · OPNsense · from source Use the web panel · programs/schedules/curves · command-line tools Reference Configuration · Authentication and pairing · REST API · Control schema Operate Exposing it safely · Reverse proxy and TLS · Troubleshooting · auth v2 Develop Architecture · Building and releasing · PoC architectures · plans docs/API.md was four references in one file and is now four pages. HARDENING.md became "Exposing it safely". Six pages are new, assembled from README material that had nowhere better to live: the panel, programs, the CLIs, architecture, building and releasing, and the vendor-app comparison with its drawbacks.
Initial Home page