aboutsummaryrefslogtreecommitdiffstats
path: root/docs/windows-build.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/windows-build.md')
-rw-r--r--docs/windows-build.md15
1 files changed, 13 insertions, 2 deletions
diff --git a/docs/windows-build.md b/docs/windows-build.md
index 88133cb..3f14664 100644
--- a/docs/windows-build.md
+++ b/docs/windows-build.md
@@ -40,7 +40,9 @@ This runs [`packaging/win/build-win.ps1`](../packaging/win/build-win.ps1), which
4. `npm run sync-ui` — copies the SPA from `meshbay-hub/.../static`
5. runs [`build-node-runtime.ps1`](../packaging/win/build-node-runtime.ps1) —
creates a throwaway venv, installs `meshbay-node` + `meshbay-common`,
- freezes the daemon with PyInstaller, fetches and verifies ffmpeg
+ freezes the daemon with PyInstaller, fetches and verifies ffmpeg, then
+ starts the frozen daemon in a throwaway profile and checks it answers
+ (`smoke-node-runtime.ps1` — also runnable against an installed build)
6. `electron-builder --win nsis`
Expect this to take several minutes the first time (Chromium download,
@@ -76,7 +78,16 @@ prompt unless you opt into service mode (background daemon that starts at
boot, before sign-in) or accept the firewall rules, both offered during setup
and both switchable afterwards from the Node page. Installs to
`%LOCALAPPDATA%\Programs\MeshBay\`; runtime data lives in
-`%LOCALAPPDATA%\meshbay\`.
+`%LOCALAPPDATA%\meshbay\`, and the node's log in
+`%LOCALAPPDATA%\meshbay\state\node.log`.
+
+Installing over a previous version stops a running node first (including a
+background-service one) and starts the new one afterwards. To check what an
+installed build actually runs:
+
+```powershell
+meshbay-node service start # waits for the node, prints the version that answered
+```
## What's not automated yet