sjg/trx-rs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[feat](trx-frontend-rigctl): per-rig rigctl listeners for multi-rig setups

Browse Source 
Add rig_ports map to RigctlFrontendConfig. When non-empty, one rigctl
TCP listener is spawned per entry instead of the single shared listener,
each routing commands to its assigned rig via rig_id_override on RigRequest.

Add rig_id_override: Option<String> to RigRequest so the remote client
can route individual requests to a specific rig without changing the
globally selected rig. build_envelope prefers the override when set.

Example config:
  [frontends.rigctl]
  enabled = true
  listen = "127.0.0.1"
  port = 4532
  rig_ports.ft817 = 4532
  rig_ports.airspyhf = 4533

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Stan Grams <sjg@haxx.space>
This commit is contained in:
Stan Grams
2026-02-28 08:41:39 +01:00
parent 2c2a0951a5
commit b5a1b4af33
10 changed files with 74 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -10
View File
@@ -12,18 +12,15 @@ Configuration reference: see `CONFIGURATION.md` for all server/client options an
## Configuration Files
`trx-server` and `trx-client` now support a shared `trx-rs.toml` as well as the legacy per-binary files.
`trx-server` and `trx-client` read configuration from a shared `trx-rs.toml`.
- Default search order for each app:
current directory, then `~/.config/trx-rs`, then `/etc/trx-rs`
- At each location, the loader checks:
`trx-rs.toml` first (`[trx-server]` or `[trx-client]` section), then the legacy flat file
- Combined file names:
`trx-rs.toml` and reads the `[trx-server]` or `[trx-client]` section
- Config file name:
`trx-rs.toml`
- Legacy flat file names:
`trx-server.toml` in the current directory, `server.toml` under XDG/`/etc`
`trx-client.toml` in the current directory, `client.toml` under XDG/`/etc`
- `--config <FILE>` still loads an explicit file path. If that file contains a `[trx-server]` or `[trx-client]` section, only that section is used; otherwise the whole file is parsed as the legacy flat format.
- `--config <FILE>` loads an explicit config file path and reads the matching `[trx-server]` or `[trx-client]` section from that file.
- `--print-config` prints an example combined config block suitable for `trx-rs.toml`.
See `trx-rs.toml.example` for a complete combined example.
@@ -46,12 +43,11 @@ The HTTP frontend supports optional passphrase-based authentication with two rol
- **rx**: Read-only access to status, events, decode history, and audio streams
- **control**: Full access including transmit control (TX/PTT) and power toggling
Authentication is disabled by default for backward compatibility. When enabled, users must log in via a passphrase before accessing the web UI. Sessions are managed server-side with configurable time-to-live and cookie security settings.
Authentication is disabled by default. When enabled, users must log in via a passphrase before accessing the web UI. Sessions are managed server-side with configurable time-to-live and cookie security settings.
### Configuration
In a combined `trx-rs.toml`, enable authentication under `[trx-client.frontends.http.auth]`.
If you use a legacy `trx-client.toml`, use the same keys under `[frontends.http.auth]`.
Enable authentication under `[trx-client.frontends.http.auth]` in `trx-rs.toml`.
```toml
[trx-client.frontends.http.auth]