Repository navigation
The stable cut of the 0.6.0-beta.1…beta.3 line. Everything below is the
beta content promoted unchanged; see the beta entries for full detail.
Highlights:
- Public status page. Publish the containers, services and servers your
customers depend on as named services, with a plain-language banner, 90-day
uptime bars, incidents with team-posted updates, and Atom and JSON feeds.
Add services straight from Monitoring. Internal names never appear publicly.
(#157) - Guided first run, Telegram optional.
sudo trinetra clion a new server
walks through the web UI, the first admin's enroll link and where alerts go.
Every step can be skipped, and Telegram is one alert channel among the
others, not a requirement. - Users from the terminal.
trinetra users list,invite,set-roleand
remove, also while the daemon is stopped. A newresponderrole sits
between viewer and admin. - Reworked web UI. Grouped sidebar, tabbed Settings, Notifications and
Updates, every page usable on a phone, and channel secrets no longer shown
(#139). - Passkeys that show up everywhere. Discoverable credentials, sign-in by
name for older keys, and no more false clone rejections (#170). - Sturdier self-update. Works on
noexecand SELinux hosts (#141), keeps
retrying a failed restore (#136), fails closed on an unreadable version floor
(#138), reports every outcome (#142), no longer offers the installed release
(#167), and the watchdog fires after reinstall (#140). - Reliability.
trinetra cliright after install waits for the daemon
(#162); the web UI recovers after sitting idle and keeps its real config
across a daemon restart; user, invite and session stores are locked across
processes; downtime history is paged server-side (#117).
Upgrading from 0.5.0
- The first admin sign-up now needs an invite link
(sudo trinetra users invite --role admin) unless the web UI is local-only.
Existing accounts are unaffected. - "View public page" now opens
/status; old/publiclinks redirect there.
Verifying this release
Every binary is listed with its SHA-256 in manifest.json, which carries two independent Ed25519 signatures: manifest.ci.sig (made by CI) and manifest.maint.sig (the maintainer's offline co-signature). trinetra update and trinetra install --require-signed check both before anything runs. Binaries also carry a GitHub build-provenance attestation:
gh attestation verify trinetra-linux-amd64 --repo InfoDiveLabs/trinetraFor manual verification with only openssl and sha256sum, see Verify a download yourself.