From 779de03b14ae5c2ed253b132ebd6b24ab3ad4685 Mon Sep 17 00:00:00 2001 From: Joerg Date: Tue, 19 May 2026 12:42:01 +0200 Subject: [PATCH] Update doc --- README.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/README.md b/README.md index c3e59fa..105d519 100644 --- a/README.md +++ b/README.md @@ -61,6 +61,35 @@ docker compose up -d To change these later, go to **Setup** as admin. +## Admin Page (`/admin`) + +The admin page provides full management of the webconsole. Only users with the **admin** role can access it. + +### User Management + +- View all users with their role, status, last seen, and last TX timestamps +- Create, edit, disable, or delete users +- Reset user passwords +- Three roles: **admin** (full access), **user** (TX/RX), **guest** (RX only) +- Safety: cannot delete yourself or the last remaining admin + +### SDR Settings + +- **PlutoSDR IP** — IP address of the Pluto (default: `192.168.6.122`) +- **LNB LO Frequency** — exact local oscillator frequency in Hz (e.g. `9749971700` for a Bullseye TCXO) +- **S-Meter Offset** — calibration offset from dBFS to dBm + +Changes trigger a reconnect to the SDR bridge. + +### TX Lock + +A global transmit lock that, when enabled, blocks all users from transmitting (PTT, two-tone, etc.) and stops any active transmissions. + +### Activity Log + +- Paginated log (200 entries per page) of all user activity +- Filterable by user and event type (login, logout, TX start/stop, disconnect, etc.) + ## Networking: Reaching the Pluto By default Docker uses bridge networking. If the Pluto is on a separate Ethernet interface the container can't route to, use host networking (Linux only):