Configuration

Configure Rugix Admin's listen address and available operations.

Rugix Admin’s configuration controls how the web service listens for connections. Rugix Ctrl’s daemon policy controls which device operations are available through the interface.

Listen Address

Rugix Admin reads /etc/rugix/admin.toml at startup. It listens on 127.0.0.1:7492 when this file is absent. To accept connections from another machine, bind it to the address of a trusted management interface:

address = "192.0.2.10:7492"

Replace the example address with one assigned to the device. Binding to 0.0.0.0:7492 exposes Rugix Admin through every network interface and should only be used when those paths are appropriately restricted.

For a system built with Rugix Bakery, include this file through a project-specific recipe. For Yocto, install it from a distribution-specific recipe or .bbappend. Otherwise, update it on the device and restart the service:

sudo systemctl restart rugix-admin.service

Unknown fields and invalid values prevent the service from starting instead of being ignored.

The --address command-line option takes precedence over admin.toml. When using the standalone installer, set RUGIX_ADMIN_ADDRESS to add this override to the installed systemd unit:

sudo env RUGIX_ADMIN_ADDRESS=127.0.0.1:7492 \
  bash install-rugix-admin.sh

Available Operations

Enable only the operations required for the device’s workflow. The controls available in Rugix Admin follow the policy enforced by the Rugix Ctrl daemon.

Use Rugix Ctrl’s Privileged Operation Daemon documentation as the authoritative reference for configuration, defaults, and the effect of each policy setting.