-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Paco5687 edited this page Jul 13, 2026
·
5 revisions
You only install the hub once. Everything else (agents) is added from the dashboard — see Onboarding Hosts.
- One always-on Linux box for the hub (a NUC, Pi, spare PC, or VM).
- The
autormm-serverbinary — from a release or built withmake build.
autormm-serverOn first run it:
- generates and saves its admin + enroll tokens (so they survive restarts),
- turns on the history database,
- prints a banner with the dashboard URL and admin token.
┌───────────────────────────────────────────────────────────┐
│ autormm is ready │
│ Dashboard: http://<hub-ip>:8765 │
│ Admin token: •••••••••••••••••••••••••• │
└───────────────────────────────────────────────────────────┘
Copy the admin token — you'll paste it into the dashboard.
Use the provided systemd user service so it starts on boot:
./deploy/install-server.sh --bin dist/autormm-server
# installs the binary + systemd unit, generates tokens, enables the serviceOr wire it up manually with deploy/systemd/autormm-server.service and
deploy/systemd/server.env.example.
Browse to http://<hub-ip>:8765, click the 🔑 icon, and paste the admin
token. See the Dashboard Guide.
Run it as plain IP:port on your LAN — no reverse proxy needed. It grants
full control of every enrolled host, so never expose it directly to the
internet. To reach it from outside your network, use a zero-trust overlay —
see Remote Access.
| What | Path |
|---|---|
| Tokens / config (auto) | ~/.config/autormm/autormm.json |
| History + scripts DB |
~/.config/autormm/autormm.db (or --db <path>) |
| Flag | Purpose |
|---|---|
-addr |
listen address (default :8765) |
-db |
SQLite path for history + scripts (on by default) |
-alert-cpu / -alert-mem / -alert-disk
|
alert thresholds (percent) |
-notify-webhook / -notify-ntfy / -notify-discord
|
alert destinations |
-tls-cert / -tls-key
|
optional built-in TLS |