Appliance operator quick reference¶
Installed configuration is authoritative. This reference uses no fixed receiver inventory or network identity. The synthetic public profile is an editable example, never a safe default for unreviewed hardware.
Inspect without starting reception¶
sdr-status
sudo sdr-demandctl status
sudo rfsentry-jobctl list
rfsentry-config show
sudo rfsentry-qos status
systemctl status rfsentry-api.service sdr-demand.service rfsentry-decoder.service
journalctl -u sdr-demand.service -n 100 --no-pager
journalctl -u rfsentry-api.service -n 100 --no-pager
Status is not proof of RF reception, physical power removal or certificate trust.
Keep diagnostic output private until reviewed; it can contain installation data.
Use sdr-demandctl --help and rfsentry-jobctl --help for explicit controls.
Receiver/job actions affect acquisition; inspect active clients first.
Install or upgrade¶
Follow the installation guide and hardware policy. A complete existing installation normally upgrades with:
Fresh installation requires reviewed private hardware and identity inputs.
Full installation interrupts clients; saved enabled jobs resume at startup.
--no-start is not a dry run: it writes/enables files and leaves services stopped.
Never use a live install to test a documentation or configuration change.
Operator guides¶
- Receiver setup and controls
- Identity, API policy and TLS
- Continuous jobs
- Record-source selection and recovery
- Storage and retention
- Clock and acquisition architecture
- Troubleshooting and failure boundaries
- Roadmap and unresolved gates
The installed convenience copies link into the locally installed static
/usr/local/share/rfsentry-web/docs/ tree. The same site is served at /docs/
on the configured appliance origin; navigation does not require GitHub.