@alook/daemon 0.1.12 → 0.1.13
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 +36 -0
- package/dist/cli/index.js +677 -96
- package/dist/index.js +928 -521
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -25,6 +25,42 @@ is what's reusable — plug in whatever host you like.
|
|
|
25
25
|
|
|
26
26
|
---
|
|
27
27
|
|
|
28
|
+
## Daemon lifecycle commands
|
|
29
|
+
|
|
30
|
+
The web Machines sheet generates the full command, including the correct HTTP
|
|
31
|
+
and WebSocket endpoints. Published-package commands use the package's explicit
|
|
32
|
+
binary so npm never guesses the wrong executable:
|
|
33
|
+
|
|
34
|
+
```sh
|
|
35
|
+
npm exec --yes --package=@alook/daemon@latest -- alook-daemon daemon start \
|
|
36
|
+
--machine-key '<cmt_pair_token>' --server-url '<https_url>' --ws-url '<wss_url>'
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
Restart a previously paired machine without rotating its credential:
|
|
40
|
+
|
|
41
|
+
```sh
|
|
42
|
+
npm exec --yes --package=@alook/daemon@latest -- alook-daemon daemon start --id '<machine_id>'
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
Reconnect/rotate only with the command generated for that exact machine:
|
|
46
|
+
|
|
47
|
+
```sh
|
|
48
|
+
npm exec --yes --package=@alook/daemon@latest -- alook-daemon daemon reconnect \
|
|
49
|
+
--id '<machine_id>' --machine-key '<cmt_reconnect_token>'
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Reconnect first takes replacement ownership and stops only the matching saved
|
|
53
|
+
PID, then activates the token. A proven pre-commit rejection resumes the prior
|
|
54
|
+
launch record. If a committed response is received and local launch then fails,
|
|
55
|
+
the newly persisted record remains offline and is recovered with
|
|
56
|
+
`daemon start --id '<machine_id>'`. A network error, timeout, 5xx, or otherwise
|
|
57
|
+
ambiguous activation response never restarts the possibly revoked old credential;
|
|
58
|
+
because the new credential was not received, mint a fresh reconnect token in the
|
|
59
|
+
UI and run `daemon reconnect` again. Never paste pairing or machine credentials
|
|
60
|
+
into logs, bug reports, or chat.
|
|
61
|
+
|
|
62
|
+
---
|
|
63
|
+
|
|
28
64
|
## The big idea
|
|
29
65
|
|
|
30
66
|
The daemon never speaks a runtime's native protocol directly. Each runtime is
|