nervur 0.37.18 → 0.37.20

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 +29 -28
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -3,22 +3,20 @@
3
3
  Nervur's one name. Software becomes organisms: one for every person, group and agent, each on a device of its own, all
4
4
  speaking Quo. This package gives the `nervur` command, by which a person lays and asks their organism.
5
5
 
6
- **0.x is unstable.** Every version before 1.0.0 may change its commands; a change that breaks them raises the minor, any
7
- other the patch.
6
+ **0.x is unstable.** Every version before 1.0.0 may change its commands, and every release raises the patch, whatever it
7
+ changes; what breaks is told in the changelog.
8
8
 
9
9
  ## Your first day
10
10
 
11
11
  From a machine with nothing to an organism you own, a faculty of yours running in a repo of yours, an owner on another
12
- device, a backup, a stop and a start. Each block is typed as it stands, in one shell. Every `bash` block is proven in
13
- order, on an account of its own with no service, before a version goes out, so a command there that stopped working
14
- never ships; an `sh` block needs what that account cannot give it, a second device or a reboot.
12
+ device, a backup, a stop and a start. Each block is typed as it stands, in one shell.
15
13
 
16
14
  ### Node and npm
17
15
 
18
- Nervur runs on Node 24 or any newer, with its npm, and is proven on Node 24. A machine with none takes it from
19
- [nodejs.org](https://nodejs.org/en/download), its v24 line: the installer on a Mac or Windows, the Linux binaries on
20
- Linux and a Pi, or your distribution's own package of Node 24. The one-command scripts of this package's `install/`
21
- folder, which lay a pinned Node themselves, are served by no address yet.
16
+ Nervur runs on Node 22.23.5 or any newer, with its npm. A machine with none takes it from
17
+ [nodejs.org](https://nodejs.org/en/download): the installer on a Mac or Windows, the Linux binaries on Linux and a
18
+ 64-bit Pi, or your distribution's own package of Node. The one-command scripts of this package's `install/` folder lay a
19
+ pinned Node of their own, for x64 and arm64, and are served by no address yet.
22
20
 
23
21
  Every Nervur package stands on npm, and no token is needed to read them. Where your Node belongs to root, make npm's
24
22
  global folder your account's own first, and put its `bin` on your `PATH`: `npm config set prefix ~/.nervur/installer`,
@@ -30,7 +28,11 @@ npm install -g nervur
30
28
 
31
29
  ### Install, own and ask
32
30
 
33
- `nervur install` lays your organism in `~/.nervur/organism/`, as a service of your account that starts it at every boot.
31
+ `nervur install` lays your organism in `~/.nervur/organism/`, as a service of your account that starts it again after
32
+ any end: on a Mac a launchd agent, started when the account logs in; on Linux a systemd user service, started at boot
33
+ where the account lingers (the install tries to turn that on); on Windows a scheduled task, started at boot and checked
34
+ every minute. Its log is `~/.nervur/organism/organism.log`.
35
+
34
36
  How it gets its boot key at each boot, its boot mode, is settled at the first install, by whether a person sits at the
35
37
  machine:
36
38
 
@@ -126,7 +128,7 @@ under `boot.key`, keep a copy of it off the device. Lose them with the device an
126
128
  backup can name keys of your own as well: the brain's `backup` takes `keys`, public keys as `nervur arrive` shows them,
127
129
  whose secrets open that backup as the boot key does and survive a rewrap, so a secret can stay on paper or with a
128
130
  partner. On a device with no organism, a restore is a new life under that device's own boot key: its lobes stand, and
129
- every relation it held is dropped, to be given again. A backup under a passphrase names its salt, and the
131
+ every relation it gave is dropped, to be given again or ended. A backup under a passphrase names its salt, and the
130
132
  restore asks the passphrase; one under `boot.key` names none, and the restore asks the line the copy of `boot.key`
131
133
  holds; then the new device asks what its own mode asks, as a first install does:
132
134
 
@@ -149,30 +151,29 @@ nervur stop
149
151
  nervur start
150
152
  ```
151
153
 
152
- ## Where it holds at this version
153
-
154
- This command is the Node installer's. The `bash` blocks above are proven, as its first day says, on a Mac, and each
155
- host below says what stands beyond that:
154
+ ## What this package is
156
155
 
157
- - **Mac:** the installer and its service, under launchd, are run on a Mac. A clean Mac, followed from nothing and
158
- rebooted, is not yet proven.
159
- - **Linux and Pi:** the service is a systemd user unit. A clean Linux machine, and a real Pi, are not yet proven.
160
- - **Windows:** not yet proven. This page does not promise it.
161
- - **browser:** the browser's port stands in a package of its own, `@nervur.org/installer-browser`, and is proven on
162
- Chromium alone. Firefox and Safari are not yet proven. There, a repo is reached from afar; this page's commands are
163
- the Node installer's.
164
- - An edge is laid by a pilot of a repo of its own, none of which is published yet: the port gives it its cargo.
156
+ This command is the Node installer's, for a Mac, Linux, a 64-bit Pi and Windows. The browser's port stands in a package
157
+ of its own, `@nervur.org/installer-browser`; there a repo is reached from afar, and this page's commands are the Node
158
+ installer's. An edge is laid by hand with `wrangler`, or by a pilot you write; the Node installer's package carries its
159
+ cargo.
165
160
 
166
161
  It holds no code of Nervur's parts: its command runs the installer of the host it is laid on,
167
162
  `@nervur.org/installer-node` on Node, which takes `@nervur.org/genome` and holds the organs. `nervur install` lays an
168
- organism in the account's home, or, as `nervur update [<version> [<digest>]]`, moves it to a version of the channel,
169
- draining its body first so no work is lost and trying the version before it is kept; `nervur start` boots it, and
170
- `nervur state` asks it through its console; `nervur` alone prints every command.
163
+ organism in the account's home, or, as `nervur update [<version> [<digest>]]`, moves it to a version of the channel: it
164
+ stops the organism at once, so a run going is lost, then tries the new version and keeps it, or goes back to the old one
165
+ if it fails; `nervur start` boots it, and `nervur state` asks it through its console; `nervur` alone prints every
166
+ command.
171
167
 
172
168
  ## Running a faculty you hold
173
169
 
174
- A faculty's text in a file enters by your own hand, and nothing runs until you create a lobe on it:
175
- `nervur lobe library add "$(jq -Rs '{source: .}' faculty.js)"` answers its digest, and
170
+ A faculty's text in a file enters by your own hand, and nothing runs until you create a lobe on it. This answers its
171
+ digest:
172
+
173
+ ```bash
174
+ nervur lobe library add "$(node -p "JSON.stringify({source: require('fs').readFileSync('faculty.js', 'utf8')})")"
175
+ ```
176
+
176
177
  `nervur ask brain create '{"faculty": "<digest>"}'` makes the lobe, whose wires you name by `wiring`. Code with no
177
178
  evidence is shown as `unproven`, never refused.
178
179
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "nervur",
3
- "version": "0.37.18",
3
+ "version": "0.37.20",
4
4
  "description": "Nervur's one name: the nervur command, on the installer of the host it is laid on. 0.x, unstable.",
5
5
  "keywords": [
6
6
  "cli",
@@ -24,7 +24,7 @@
24
24
  "access": "public"
25
25
  },
26
26
  "dependencies": {
27
- "@nervur.org/installer-node": "0.37.18"
27
+ "@nervur.org/installer-node": "0.37.20"
28
28
  },
29
29
  "engines": {
30
30
  "node": ">=22.23.5"