@runeditrun/rer 0.2.34 → 0.2.35
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 +21 -7
- package/global/CHANGELOG.md +10 -0
- package/global/README.md +21 -7
- package/install.sh +7 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,14 +6,25 @@ checkout always gets the behaviour it was built and tested with.
|
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
|
-
Start a seed from an empty folder with
|
|
9
|
+
Start a seed from an empty folder, with or without Node:
|
|
10
|
+
|
|
11
|
+
```sh
|
|
12
|
+
curl -fsSL https://runeditrun.com/install.sh | sh
|
|
13
|
+
rer dev just-every/run-inkwell
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
The installer needs no Node: without Node 22 or later on PATH it installs a
|
|
17
|
+
private one for `rer` (see below). It edits no shell profile, so when
|
|
18
|
+
`~/.local/bin` is not on PATH, run the `export PATH=…` line it prints before
|
|
19
|
+
`rer dev`. Its last line names that next command. The same start also fits on
|
|
20
|
+
one line:
|
|
10
21
|
|
|
11
22
|
```sh
|
|
12
|
-
npx -y @runeditrun/rer dev just-every/run-inkwell
|
|
13
23
|
curl -fsSL https://runeditrun.com/install.sh | sh -s -- dev just-every/run-inkwell
|
|
24
|
+
npx -y @runeditrun/rer dev just-every/run-inkwell # only with Node 22 or later on PATH
|
|
14
25
|
```
|
|
15
26
|
|
|
16
|
-
|
|
27
|
+
Each of these installs the user CLI, clones into `./run-inkwell`, install dependencies, set
|
|
17
28
|
up a local owner and start the app. Open the printed `RER_OPEN` link to sign in.
|
|
18
29
|
Use `setup <repo>` to stop after setup, or `install <repo>` to stop after
|
|
19
30
|
dependency installation; each prints the next command. The repo can be
|
|
@@ -27,9 +38,9 @@ leaves the app running. The restart command includes `cd` into the checkout.
|
|
|
27
38
|
Install `rer` with one of these commands:
|
|
28
39
|
|
|
29
40
|
```sh
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
npm install -g @runeditrun/rer # npm's own global layout
|
|
41
|
+
curl -fsSL https://runeditrun.com/install.sh | sh # user install in ~/.local/share/rer, launcher ~/.local/bin/rer; no Node needed
|
|
42
|
+
npx -y @runeditrun/rer cli install # the same user install, with Node 22 or later on PATH
|
|
43
|
+
npm install -g @runeditrun/rer # npm's own global layout, with Node 22 or later on PATH
|
|
33
44
|
```
|
|
34
45
|
|
|
35
46
|
`install.sh` is the file at the root of this package. It reads the version, the
|
|
@@ -44,7 +55,10 @@ With no Node 22 or later on PATH, the script installs Node 22.20.0 from
|
|
|
44
55
|
`nodejs.org` into `~/.local/share/rer/runtimes` (under `XDG_DATA_HOME` when set),
|
|
45
56
|
verifies the tarball against that release's published `SHASUMS256.txt`, and
|
|
46
57
|
prints its location. The launcher uses this private runtime on later runs.
|
|
47
|
-
System Node and other PATH directories are left alone
|
|
58
|
+
System Node and other PATH directories are left alone: the private runtime's
|
|
59
|
+
`node`, `npm` and `npx` are not put on PATH, because `rer` is the one command
|
|
60
|
+
the installer provides. With no arguments the script ends by naming the next
|
|
61
|
+
command, `rer dev <owner>/<repo>`.
|
|
48
62
|
|
|
49
63
|
No installer edits shell profiles. The canonical launcher is `~/.local/bin/rer`.
|
|
50
64
|
Installation creates that directory if needed and never writes into another
|
package/global/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.35
|
|
4
|
+
|
|
5
|
+
- **The Run page starts a seed without Node.** The shared /run page has two steps. Step 1 is `curl -fsSL https://runeditrun.com/install.sh | sh`, which brings its own Node and changes no shell settings. Step 2 is `rer dev <owner>/<repo>`, with `cd <folder> && rer dev` to start it again later. `npx -y @runeditrun/rer dev <owner>/<repo>` remains only as the alternative under "Already have Node 22 or later?". Before this, a newcomer without Node got `sh: npx: command not found` at step 2, because the installer keeps its Node private. Step 2 is built from Run data's existing `clone` line, so seeds need no edits. RUN-LOCALLY, HOMEPAGE-VARIANTS, SEED-COMMAND-CONTRACT and the READMEs describe the two steps, and the default and foundation Run requirements no longer say "Needs Node 22".
|
|
6
|
+
- **install.sh names the next step.** Run with no arguments, `install.sh` now ends with `Next, start a seed: rer dev <owner>/<repo>`. It still puts no `node`, `npm` or `npx` on PATH.
|
|
7
|
+
|
|
8
|
+
### Upgrade notes
|
|
9
|
+
|
|
10
|
+
- A seed refreshes its copy of the /run page and docs from Base to get the two steps.
|
|
11
|
+
- The installer served at runeditrun.com takes its text from the published package, so the Next line arrives with this release.
|
|
12
|
+
|
|
3
13
|
## 0.2.34
|
|
4
14
|
|
|
5
15
|
- **Optional deploy secrets.** A deploy declaration's secret entry may add `"optional": true` for an integration's credential (Pier, Stripe). When neither the Worker nor the deploy inputs hold it, the first deploy succeeds without binding it and reports `Optional secrets not set: NAME`, and a dry run names optional secrets that were not supplied. Health waits only for required secrets, and a missing required secret still refuses before any write. `rer deploy --set-secret NAME` and `--unset-secret NAME` record the Worker version they make, so the next deploy accepts that Worker and an unchanged repeat writes nothing. A declaration without `optional` plans and fingerprints exactly as before.
|
package/global/README.md
CHANGED
|
@@ -6,14 +6,25 @@ checkout always gets the behaviour it was built and tested with.
|
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
|
-
Start a seed from an empty folder with
|
|
9
|
+
Start a seed from an empty folder, with or without Node:
|
|
10
|
+
|
|
11
|
+
```sh
|
|
12
|
+
curl -fsSL https://runeditrun.com/install.sh | sh
|
|
13
|
+
rer dev just-every/run-inkwell
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
The installer needs no Node: without Node 22 or later on PATH it installs a
|
|
17
|
+
private one for `rer` (see below). It edits no shell profile, so when
|
|
18
|
+
`~/.local/bin` is not on PATH, run the `export PATH=…` line it prints before
|
|
19
|
+
`rer dev`. Its last line names that next command. The same start also fits on
|
|
20
|
+
one line:
|
|
10
21
|
|
|
11
22
|
```sh
|
|
12
|
-
npx -y @runeditrun/rer dev just-every/run-inkwell
|
|
13
23
|
curl -fsSL https://runeditrun.com/install.sh | sh -s -- dev just-every/run-inkwell
|
|
24
|
+
npx -y @runeditrun/rer dev just-every/run-inkwell # only with Node 22 or later on PATH
|
|
14
25
|
```
|
|
15
26
|
|
|
16
|
-
|
|
27
|
+
Each of these installs the user CLI, clones into `./run-inkwell`, install dependencies, set
|
|
17
28
|
up a local owner and start the app. Open the printed `RER_OPEN` link to sign in.
|
|
18
29
|
Use `setup <repo>` to stop after setup, or `install <repo>` to stop after
|
|
19
30
|
dependency installation; each prints the next command. The repo can be
|
|
@@ -27,9 +38,9 @@ leaves the app running. The restart command includes `cd` into the checkout.
|
|
|
27
38
|
Install `rer` with one of these commands:
|
|
28
39
|
|
|
29
40
|
```sh
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
npm install -g @runeditrun/rer # npm's own global layout
|
|
41
|
+
curl -fsSL https://runeditrun.com/install.sh | sh # user install in ~/.local/share/rer, launcher ~/.local/bin/rer; no Node needed
|
|
42
|
+
npx -y @runeditrun/rer cli install # the same user install, with Node 22 or later on PATH
|
|
43
|
+
npm install -g @runeditrun/rer # npm's own global layout, with Node 22 or later on PATH
|
|
33
44
|
```
|
|
34
45
|
|
|
35
46
|
`install.sh` is the file at the root of this package. It reads the version, the
|
|
@@ -44,7 +55,10 @@ With no Node 22 or later on PATH, the script installs Node 22.20.0 from
|
|
|
44
55
|
`nodejs.org` into `~/.local/share/rer/runtimes` (under `XDG_DATA_HOME` when set),
|
|
45
56
|
verifies the tarball against that release's published `SHASUMS256.txt`, and
|
|
46
57
|
prints its location. The launcher uses this private runtime on later runs.
|
|
47
|
-
System Node and other PATH directories are left alone
|
|
58
|
+
System Node and other PATH directories are left alone: the private runtime's
|
|
59
|
+
`node`, `npm` and `npx` are not put on PATH, because `rer` is the one command
|
|
60
|
+
the installer provides. With no arguments the script ends by naming the next
|
|
61
|
+
command, `rer dev <owner>/<repo>`.
|
|
48
62
|
|
|
49
63
|
No installer edits shell profiles. The canonical launcher is `~/.local/bin/rer`.
|
|
50
64
|
Installation creates that directory if needed and never writes into another
|
package/install.sh
CHANGED
|
@@ -141,11 +141,14 @@ NODE
|
|
|
141
141
|
tar -xzf "$work/rer.tgz" -C "$work/stage" || fail "could not unpack rer $version; nothing was installed."
|
|
142
142
|
RER_INSTALL_CHANNEL=script node "$work/stage/package/global/rer.mjs" cli install </dev/null \
|
|
143
143
|
|| fail "rer cli install failed; any previous install is still selected."
|
|
144
|
-
if [ "$#" -
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
144
|
+
if [ "$#" -eq 0 ]; then
|
|
145
|
+
# The same next step a Run page gives; no npx, since Node may be rer's own.
|
|
146
|
+
printf 'Next, start a seed: rer dev <owner>/<repo>\n'
|
|
147
|
+
return
|
|
148
148
|
fi
|
|
149
|
+
PATH="$HOME/.local/bin:$PATH"
|
|
150
|
+
export PATH
|
|
151
|
+
"$HOME/.local/bin/rer" "$@"
|
|
149
152
|
}
|
|
150
153
|
|
|
151
154
|
install_node() {
|