aboutsummaryrefslogtreecommitdiffstats
path: root/packaging/build/build-node.sh
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-04 14:42:05 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-05 13:32:00 +0200
commitf808cf0ecaa3c6db023b1496f4b09cca5ca934f9 (patch)
treec9ac2cec4f4fb4349ad1884a27d574a56b7858a2 /packaging/build/build-node.sh
parente89a57bb97b5a0d624e8d490b6b8aa38ba140817 (diff)
downloadmeshbay-f808cf0ecaa3c6db023b1496f4b09cca5ca934f9.tar.gz
docs(packaging): correct four claims the README makes about the build
Checked every instruction in packaging/README.md against the code. Four were wrong; the rest hold. - `meshbay-hub --generate-keys` does not exist. The hub CLI takes --config, --log-level and a prune-groups subcommand, so the documented first step of the hub install fails with "unrecognized arguments". It is also unnecessary: app.py's lifespan generates the keypair on first start when the file is absent. Step removed, behaviour documented instead. - The systemd table named two source files that do not exist. The system unit is built from systemd/meshbay-node.service and *installed as* meshbay-node@.service; the user unit comes from meshbay-node-user.service. Only the destination column was right. - The output line pinned 0.9.0; every package is 0.10.0. Replaced with <version> so it cannot go stale again, and MESHBAY_BUILD_DIR is mentioned. - The firewall section documented only the client's casting profile. It now covers the node profile added in 40abf09, with the LAN scoping that profile requires. Verified as accurate and left alone: the /tmp/meshbay-build/out/ path, the install order, hub.toml.example, the desktop file, and the default.env claim (true as of c2eade6, which implemented the copy it described). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtfG7z6wHWj8RKHCvxQtY1
Diffstat (limited to 'packaging/build/build-node.sh')
0 files changed, 0 insertions, 0 deletions