@slayzone/cli 0.36.0-beta.17 → 0.36.0-beta.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -14
- package/dist/slay.js +941 -723
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -18,27 +18,26 @@ systemd --user on Linux), so it restarts if it crashes and starts again when you
|
|
|
18
18
|
log in. Names are unique per machine — `create` fails if one already exists. To
|
|
19
19
|
run a hub in the foreground instead, use `npx @slayzone/hub`.
|
|
20
20
|
|
|
21
|
-
##
|
|
21
|
+
## Computers on this machine
|
|
22
22
|
|
|
23
|
-
A
|
|
23
|
+
A computer is an execution node: it dials out to a hub and runs terminals, agents
|
|
24
24
|
and git there. Mint a join token on the hub, then:
|
|
25
25
|
|
|
26
|
-
slay
|
|
27
|
-
slay
|
|
28
|
-
slay
|
|
29
|
-
slay
|
|
30
|
-
slay
|
|
31
|
-
slay
|
|
26
|
+
slay computer create <name> --token <szjt1…> # install it here and keep it running
|
|
27
|
+
slay computer ls # every computer installed on this machine
|
|
28
|
+
slay computer logs <name>
|
|
29
|
+
slay computer stop <name> # stop it, keep it registered
|
|
30
|
+
slay computer start <name> # bring a stopped computer back
|
|
31
|
+
slay computer rm <name> # stop it and remove its registration
|
|
32
32
|
|
|
33
|
-
The token embeds the hub URL
|
|
34
|
-
|
|
35
|
-
the service unit. `--root <dir>` picks where the runner's config, credentials and
|
|
33
|
+
The token embeds the hub URL, so `--token` is the only configuration needed. It is stored in `<root>/config.json` (owner-only) — never in
|
|
34
|
+
the service unit. `--root <dir>` picks where the computer's config, credentials and
|
|
36
35
|
logs live (default: the current directory), and `--allow <dir>` (repeatable) sets
|
|
37
|
-
the filesystem roots it may touch. One
|
|
36
|
+
the filesystem roots it may touch. One computer per root.
|
|
38
37
|
|
|
39
|
-
`create` waits until the
|
|
38
|
+
`create` waits until the computer has actually reached its hub, and unregisters
|
|
40
39
|
itself again if it cannot — so a bad token fails loudly instead of leaving a
|
|
41
|
-
service that retries forever. `rm` leaves the
|
|
40
|
+
service that retries forever. `rm` leaves the computer's data on disk and does NOT
|
|
42
41
|
revoke it on the hub; revoke it there if the machine is going away.
|
|
43
42
|
|
|
44
43
|
## Targeting a hub
|