aboutsummaryrefslogtreecommitdiffstats
path: root/docs/PACKAGING-GUIDE.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/PACKAGING-GUIDE.md')
-rw-r--r--docs/PACKAGING-GUIDE.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/PACKAGING-GUIDE.md b/docs/PACKAGING-GUIDE.md
index 56504d4..c4f6b00 100644
--- a/docs/PACKAGING-GUIDE.md
+++ b/docs/PACKAGING-GUIDE.md
@@ -66,9 +66,16 @@ node (with `meshbay-common` inside it). There is no Windows hub.
### Install
-Run the installer. It is **per-user** — no administrator prompt — and lands in
-`%LOCALAPPDATA%\Programs\meshbay-client\`. The node daemon ships beside the app
-at `resources\node-runtime\meshbay-node.exe`; the client finds it automatically.
+Run the installer. It is **per-user** and lands in
+`%LOCALAPPDATA%\Programs\meshbay-client\` without needing admin rights. The
+node daemon ships beside the app at `resources\node-runtime\meshbay-node.exe`;
+the client finds it automatically.
+
+It does ask one thing: **"Allow MeshBay through Windows Firewall now?"** —
+say yes and one administrator confirmation adds both inbound rules the client
+and the node need for WebRTC. Say no and the install finishes the same either
+way; Windows will show its own "Allow access" dialog instead, once for each,
+the first time they actually need to accept a connection.
**ffmpeg** is required for video streaming and is *not* in the installer unless
it was built with `-FfmpegDir`. Otherwise install it separately