4 - Installing

Installing

One Manager per device supervises the workers and holds the keys. You'll wrap this in a proper installer; here's what it drives.

First run

XRUIOS.Manager login     # create / unlock the account; seals the key to this OS session
XRUIOS.Manager start     # launch detached in the background
XRUIOS.Manager status    # RUNNING / stopped
XRUIOS.Manager stop

login first-time-creates the account (username + XRUIOS password) and writes the public login file. After that, login unlocks it and seals the key so start/run come up already unlocked. No login and the Manager runs locked - no workers.

Auto-start

Command What it registers
XRUIOS.Manager install At logon, user session. Windows Scheduled Task, or a systemd --user unit on Linux. Runs as the logged-in user, so it can create OS accounts and see the desktop.
deploy/windows/install-service.ps1 (as Administrator) At boot, session 0. A Windows Service that survives logout.
XRUIOS.Manager uninstall / uninstall-service Remove either.

The deploy folder has the ready scripts: deploy/windows/install-autostart.ps1, deploy/windows/install-service.ps1, and deploy/linux/xruios.service.

Where things live

  • Data + keys: %LocalAppData%\XRUIOS\ (Data, Public, Permissions, Baselines).
  • Workers: found next to the Manager, or point XRUIOS_WORKERS_ROOT at the deploy folder so the Manager can launch them.

The intended flow for your installer

  1. Lay down the Manager, the ~27 worker exes, and libs/ together (or set XRUIOS_WORKERS_ROOT).
  2. Prompt the user to create their XRUIOS account (login).
  3. Register autostart - a logon task for a normal desktop, or the service for an always-on machine.
  4. On next start the Manager unlocks, checksums and launches each worker (each with its own key + password), and the broker is up.

Back to the start: 1 - Welcome.