@zerwiz/ymir 0.1.2 → 0.1.3

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 +14 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -14,13 +14,24 @@
14
14
  > One command stands it up on your own machine. No hosting, no accounts.
15
15
 
16
16
  ```bash
17
- # curl
17
+ # 1 · curl — fetch the bootstrap and run it
18
18
  curl -fsSL https://raw.githubusercontent.com/zerwiz/ymir-release/main/install.sh | bash
19
19
 
20
- # npm
21
- npx @zerwiz/ymir # add --check to see the plan, --yes to run unattended
20
+ # 2 · npx — no install, run once
21
+ npx @zerwiz/ymir # add --check (report only) or --yes (unattended)
22
+
23
+ # 3 · npm global — install the command, then run it
24
+ npm i -g @zerwiz/ymir
25
+ ymir
26
+
27
+ # 4 · clone the distro and run its installer directly
28
+ git clone https://github.com/zerwiz/ymir.git ~/.ymir
29
+ bash ~/.ymir/bin/ymir-install.sh
22
30
  ```
23
31
 
32
+ > All four run the **same installer**. It is idempotent — run it again and it heals
33
+ > forward. `--check` shows the plan without writing anything.
34
+
24
35
  This npm package is only the **bootstrap** (install.sh + a thin `ymir` bin): it
25
36
  fetches the Ymir distro and runs its installer, which provisions, self-heals and
26
37
  **validates** what it claims is running. It carries no secrets.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zerwiz/ymir",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Ymir — the official local installer (curl | bash, or npx ymir)",
5
5
  "type": "module",
6
6
  "bin": {