Context
When Mast is deployed (e.g. as an LXC), the operator might reasonably want to manage that host from Mast itself — patch tracking, uptime, etc. Today there's no nudge; you have to know to add localhost manually with an SSH key.
Idea
During onboarding (or as a one-time dismissible banner on the servers page when the fleet is empty), offer: "Manage the host Mast is running on?" If yes, pre-fill the add-server form with 127.0.0.1 / detected hostname and let the user pick a key.
Why this is parked
For a single-host control-plane deploy this matters. For the more common "Mast watches N other boxes" setup, it's noise. Self-monitoring only really pays off once ADR 0004 (Elixir-native monitoring) lands and Mast can observe its own release — at that point "add yourself" becomes the natural default and the prompt earns its keep.
Done when
- Empty-fleet onboarding offers a one-click "add this host" path
- Pre-fills sensible defaults (host, suggested user, port)
- Dismissible; doesn't reappear after first server is added
- Linked from / informed by the self-monitoring work in ADR 0004
Related
- ADR 0004 — Elixir-native monitoring (proposed)
Context
When Mast is deployed (e.g. as an LXC), the operator might reasonably want to manage that host from Mast itself — patch tracking, uptime, etc. Today there's no nudge; you have to know to add localhost manually with an SSH key.
Idea
During onboarding (or as a one-time dismissible banner on the servers page when the fleet is empty), offer: "Manage the host Mast is running on?" If yes, pre-fill the add-server form with
127.0.0.1/ detected hostname and let the user pick a key.Why this is parked
For a single-host control-plane deploy this matters. For the more common "Mast watches N other boxes" setup, it's noise. Self-monitoring only really pays off once ADR 0004 (Elixir-native monitoring) lands and Mast can observe its own release — at that point "add yourself" becomes the natural default and the prompt earns its keep.
Done when
Related