mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

swarmctl setup status shows progress at a glance

Browse source
This commit is contained in:
atlas 2026-11-09 10:31:27 +01:00 • committed by mara
commit d55cf9ed80
2 changed files with 269 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/1-getting-started/setup.md
View file

@ -18,7 +18,7 @@ wait for you. The sections below are the same steps by hand.
Run `swarmctl setup status` at any point to see how far you have got. It lists
the hand steps below, numbered 1 to 10 in the order the sections run them, marks
each done, not done or unknown, and names the next one. It changes nothing.
each done, not done or unknown, shows a progress bar, and names the next one. It changes nothing.
> **Not all-local?** Each step says which host it runs on. A split swarm
> also has credentials you can't generate where they're read — each

4
docs/2-handbook/swarm/swarmctl-cli.md
View file

@ -658,7 +658,7 @@ For scripts, use `setup status` and the individual verbs.
###### **Subcommands:**
* `status` — Print each step of the first-run setup, in order, as `done`, `not done` or `unknown`, and what to do next
* `status` — Print the first-run setup as a progress report: a count and a bar, then each step as done, not done or unknown, and what to do next
###### **Options:**
@ -670,7 +670,7 @@ For scripts, use `setup status` and the individual verbs.
## `swarmctl setup status`
Print each step of the first-run setup, in order, as `done`, `not done` or `unknown`, and what to do next.
Print the first-run setup as a progress report: a count and a bar, then each step as done, not done or unknown, and what to do next.
Read-only, and needs no token. The secret store's steps come from `bao status` and systemd, so they show only on the host running swarm-bao; the SSO account comes from authelia's users file, on its host; ruth and the other agents come from the swarm-controller. When a check can't run, its steps print `unknown` with the reason, and the rest still print. Steps 7 and 8, the browser login and the forge site admin, always print `unknown (not observable)`.