@muhkoo/cli 0.14.0-alpha.4 → 0.14.0-alpha.6

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.
Files changed (2) hide show
  1. package/README.md +30 -4
  2. package/package.json +4 -3
package/README.md CHANGED
@@ -9,11 +9,15 @@ Built on top of [`@muhkoo/connect`](https://www.npmjs.com/package/@muhkoo/connec
9
9
  ## Install
10
10
 
11
11
  ```bash
12
- npm install -g @muhkoo/cli
12
+ npm install -g @muhkoo/cli@alpha
13
13
  # or run without installing:
14
- npx @muhkoo/cli --help
14
+ npx @muhkoo/cli@alpha --help
15
15
  ```
16
16
 
17
+ Ask for the **`alpha`** tag explicitly. `latest` still points at the older
18
+ `0.13.2-alpha.0` line, so a bare install gets a CLI without the commands
19
+ documented here.
20
+
17
21
  Requires Node.js 20+.
18
22
 
19
23
  ## Quickstart
@@ -62,6 +66,27 @@ in `~/.muhkoo/config.json`. You can override per-invocation:
62
66
  `deploy` also accepts an app **secret key** (`--key mk_*_sk_*` or `MUHKOO_DEPLOY_KEY`),
63
67
  which is what CI typically uses.
64
68
 
69
+ ### Paired machines
70
+
71
+ Commands that open your encrypted filesystem (`vfs`, `vcs`, and `devices`
72
+ itself) need the master seed as well as a session, and the seed is never stored
73
+ on disk. The first such command signs you in once and **pairs this machine**: it
74
+ generates a key here,
75
+ asks the vault to hold your seed wrapped under it, and keeps only the key. So
76
+ nothing on this disk is the seed, and the pairing can be withdrawn from anywhere
77
+ — which a stored seed never could be, because nothing can reach out and un-store
78
+ it.
79
+
80
+ ```bash
81
+ muhkoo devices ls # paired machines; the current one is marked
82
+ muhkoo devices rm <factorId> # withdraw access — takes effect immediately
83
+ ```
84
+
85
+ Revoking the machine you are on also clears its now-useless local key, so the
86
+ next filesystem command pairs again from scratch rather than retrying a pairing
87
+ the server has forgotten. `MUHKOO_SEED` bypasses pairing entirely, for CI, where
88
+ there is no interactive login to pair with.
89
+
65
90
  ## Environments
66
91
 
67
92
  `--base` selects the API base for any command:
@@ -77,9 +102,10 @@ muhkoo whoami --base https://api.example.com
77
102
  ## Commands
78
103
 
79
104
  ```
80
- Account login · logout · whoami
81
- Apps apps ls|get|create|slug|rm · keys rotate
105
+ Account login · logout · devices ls|rm · whoami
106
+ Apps apps ls|get|create|slug|rm · keys rotate · tokens ls|create|revoke
82
107
  Backend provision · tables · agents · functions
108
+ Files vfs ls|cat|put|get|rm|cp|mv|find|history|restore · vcs status|commit|log|diff|branch|switch|merge
83
109
  Hosting deploy · promote · hosting status|rollback|rm-release|unpublish · domains
84
110
  Tools logs · eject
85
111
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@muhkoo/cli",
3
- "version": "0.14.0-alpha.4",
3
+ "version": "0.14.0-alpha.6",
4
4
  "description": "Command-line interface for the Muhkoo platform — provision backends, deploy apps, and manage agents, functions, databases, and domains.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -36,10 +36,11 @@
36
36
  "lint": "node --check bin/muhkoo.js",
37
37
  "sync-version": "node scripts/sync-version.mjs",
38
38
  "prepublishOnly": "node scripts/sync-version.mjs --check",
39
- "test": "vitest run"
39
+ "test": "vitest run",
40
+ "release": "npm publish --tag alpha && npm dist-tag add @muhkoo/cli@$npm_package_version latest"
40
41
  },
41
42
  "dependencies": {
42
- "@muhkoo/connect": "0.14.0-alpha.4",
43
+ "@muhkoo/connect": "0.14.0-alpha.6",
43
44
  "snarkjs": "^0.7.0"
44
45
  },
45
46
  "packageManager": "yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e",