OverviewFilesCommitsIssuesDocsReleasesPeers

pgh commits / f2024d6

docs: second audit pass — execution-verified two more fixes
Ran the flow in an isolated temp HOME against the real checkouts: - bare does NOT need to be on PATH. `pgh app adopt` runs under bare, so resolveRuntimePath returns process.execPath and the generated launcher embeds the ABSOLUTE bare path (bare-runtime-<arch>/bin/bare). Proven: the full adopt flow runs with no `bare` on PATH. Drop the misleading ~/.local/bin/bare symlink step; keep only the (still-required) ~/.local/bin-on-PATH note for the pgh/pgh-sidecar launchers. - Quick install (tarball path): nothing auto-spawns pgh-sidecar — the CLI just connects to ~/.pgh/svc.sock and daemon commands fail if it's down; `pgh init` does not start it. Add the missing `pgh app boot` step and correct the prose. Also re-verified: the file: dep graph is exactly the 8-repo closed set (no missed edges), npm relative-symlinks each file: dep, and the adopt manifest/launcher are well-formed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
f2024d6dec0d70e68a14cd6b693a0b10696e3b47
by plankatron <fleeky@gmail.com> · 2026-07-20T03:17:01.000Z

Changed files (1) +16 -9

README.md +16 -9
……@@ -51,11 +51,13 @@ refuses to continue if the store's filesystem can't host a socket + symlink.
5151```bash
5252curl -sSfL https://7rnx.net/git/bootstrap/install.sh | sh
5353pgh init
54pgh app boot
5455```
5556
56That installs `pgh` + `pgh-sidecar` into `~/.local/bin/` (no root), then
57`pgh init` bootstraps the local registries and starts the sidecar daemon.
58Make sure `~/.local/bin` is on your `PATH`.
57That installs `pgh` + `pgh-sidecar` into `~/.local/bin/` (no root). `pgh init`
58then sets up your identity, tree store, and local registries; `pgh app boot`
59starts the `pgh-sidecar` daemon (`init` itself does **not** start it). Make
60sure `~/.local/bin` is on your `PATH`.
5961
6062Other install forms (pinned version, local tarball, custom prefix) are in
6163[`docs/overview.md`](./docs/overview.md).
……@@ -133,17 +135,22 @@ for pkg in hyper-overlay hyper-rooms hyper-svc hyper-deploy \
133135done
134136```
135137
136`bare-runtime` drops a `bare` binary at `pgh/node_modules/.bin/bare`. pgh's
137launchers resolve `bare` from your `PATH`, so put one there — either install
138it globally (`npm i -g bare-runtime`) or symlink the one you just built:
138`npm install` also drops a `bare` binary at `pgh/node_modules/.bin/bare` (via
139`bare-runtime`). You invoke it explicitly in the next step, and `pgh app adopt`
140bakes that runtime's **absolute** path into the launchers it writes — so `bare`
141does **not** need to be on your `PATH` (verified: the flow runs with no `bare`
142on `PATH` at all).
143
144`~/.local/bin` **does** need to be on your `PATH` — that's where the `pgh` and
145`pgh-sidecar` launchers land:
139146
140147```bash
141148mkdir -p ~/.local/bin
142ln -sf "$PWD/pgh/node_modules/.bin/bare" ~/.local/bin/bare
149export PATH="$HOME/.local/bin:$PATH" # add to your shell rc to persist
143150```
144151
145`~/.local/bin` must be on your `PATH` for the `pgh` / `bare` launchers to
146resolve (add `export PATH="$HOME/.local/bin:$PATH"` to your shell rc if not).
152(Optional: `npm i -g bare-runtime` if you want a standalone `bare` command on
153your `PATH` for other bare programs — the pgh launchers don't rely on it.)
147154
148155### 4. Register the source trees and initialise
149156