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.md30
1 files changed, 27 insertions, 3 deletions
diff --git a/docs/PACKAGING-GUIDE.md b/docs/PACKAGING-GUIDE.md
index fdc0a57..9f5d6cf 100644
--- a/docs/PACKAGING-GUIDE.md
+++ b/docs/PACKAGING-GUIDE.md
@@ -102,10 +102,13 @@ Two cases where the app does not do it on its own, because it would undo
something:
- the node was already set up for **another account or another hub** — the
- **Start** button on the Node page asks before switching it;
+ Node page says so, and **Use this node for my account** asks before
+ switching it;
- your account is already linked to a node on **another machine** — linking
- this one would disconnect that one. The Node page shows this node's key;
- **Profile → Link Node** moves the link here if that is what you want.
+ this one would disconnect that one. The Node page says so, and **Link this
+ node instead** asks before moving the link here. **Profile → Unlink** lets
+ go of the other machine's node from anywhere, which is the way out when that
+ machine is gone.
The Node page's **Start / Stop / Restart** work in every mode, and its status
is the node's own: **Running** when it answers, **Stopped** only once no
@@ -127,6 +130,27 @@ firewall rules and the boot-time service task with one administrator
confirmation (none if neither is there). None of this touches
`%LOCALAPPDATA%\meshbay\` (the keystore).
+### Microsoft Store version
+
+The same client and node, installed from the Microsoft Store. It never asks
+for administrator rights, and Windows itself manages what the installer above
+sets up with scripts:
+
+- **Firewall**: the rules for the node are part of the package. Windows adds
+ them at install, keeps them through updates and removes them with the app.
+- **When the node runs**: **Only while MeshBay is open** (the default) or
+ **At sign-in**, chosen on the **Node** page. At sign-in is the
+ *MeshBay Node* entry of **Settings → Apps → Startup**; switching it off
+ there is the same as choosing **Only while MeshBay is open**, and the Node
+ page cannot switch it back on until it is on there again.
+- **At boot, before anyone signs in, is not available**: it needs the
+ `.exe` installer above.
+- **`meshbay-node` in a terminal** works as with the installer.
+
+Runtime data lives in the same `%LOCALAPPDATA%\meshbay\` and survives
+uninstalling the app. Uninstall from **Settings → Apps**; it removes the
+firewall rules and the sign-in entry with it.
+
### Build from source
See [`packaging/win/README.md`](../packaging/win/README.md). On a machine with