Introduction

Rugix Admin is a browser-based management interface for systems running Rugix Ctrl. It gives operators and developers a local web UI for inspecting a device, installing updates, managing app workloads, reviewing component compatibility, and following long-running jobs.

Rugix Admin is intentionally small: it is a single service that serves a React frontend and talks to rugix-ctrl on the same device. It does not replace Rugix Ctrl, Rugix Bakery, or a fleet-management backend. Instead, it makes the on-device Rugix capabilities easier to operate when you are working locally, doing field service, building demos, or debugging a device.

What Rugix Admin Does

Rugix Admin focuses on the operations that are useful on one device:

• System status. Inspect boot groups, slots, stored hashes, and persistent-state status, including ephemeral fallback errors.
• System updates. Install uploaded or remote system bundles with Rugix Ctrl’s boot-group, overlay, reboot, verification, compatibility, range-request, and HTTP retry controls.
• System actions. Commit the active system, reboot, reboot into the spare system, or reset state with an optional state-profile backup.
• Application management. Inspect live workload health, persisted lifecycle state, generations, and metadata; install uploaded or remote bundles; and activate, deactivate, start, stop, roll back, garbage collect one or all apps, or remove apps.
• Component compatibility. Review scanned roots, loaded components, capabilities, claims, and consistency problems.
• Job tracking. Follow queued and running operations with progress, status, and command output.

Because Rugix Admin shells out to rugix-ctrl, the command-line tool remains the source of truth. The installed HTTP service runs as an unprivileged user; Rugix Ctrl forwards its supported commands to the privileged operation daemon over a group-restricted Unix socket. Rugix Admin queries the daemon’s effective policy and displays only the optional operation families it enables.

The daemon accepts signed system and application installations without an additional feature flag. Enabling dangerously-insecure in the daemon permits callers to bypass Rugix Ctrl’s verification and compatibility checks; Rugix Admin displays a red development-only warning when that policy is active.

Rugix Admin exposes every operation supported by the privileged daemon. Rugix Ctrl commands that only operate locally, such as low-level slot maintenance, boot marking, application recovery, and index creation, are outside the daemon protocol and remain command-line workflows.

What Rugix Admin Does Not Do

Rugix Admin is deliberately not a fleet manager. It does not connect devices to a cloud backend, schedule staged rollouts, manage credentials for remote fleets, or store long-term fleet history. Use a fleet-management solution for those responsibilities.

Where to Start

Install and run Rugix Admin on the device next to rugix-ctrl, then open http://<device-address>:7492/ in a browser. See HTTP API for the current status of the internal HTTP API.