Keep HTTP MCP startup independent of ambient WebSocket packages
This commit is contained in:
1 parent
e84362b999
commit
b0340869a7
12 files changed
+207
-38
No files matched your search
@@ -1,6 +1,6 @@
|
||||
# FrameBridge — Debian, Ubuntu and Linux Mint installation and first use
|
||||
|
||||
Version: 0.3.2~compat.20261027.2 | Guide schema: 1
|
||||
Version: 0.3.2~compat.20261027.3 | Guide schema: 1
|
||||
|
||||
This reference is generated from the shared CLI/MCP guide. Use the matching installed version.
|
||||
|
||||
@@ -36,7 +36,7 @@ fb --json status
|
||||
Install the .deb built for your exact Debian 13, Ubuntu 24.04/26.04, Linux Mint 22.x or LMDE 7 amd64 profile. These compatibility candidates still require installation and lifecycle validation on each target. Select the artifact from the matching profile folder and keep the distribution system Python. Normal first connection does not require a separate setup, doctor or start sequence. Run connect in a normal interactive terminal; advanced setup is optional for central/node roles and public settings.
|
||||
|
||||
~~~sh
|
||||
sudo apt install ./framebridge-expanded_0.3.2~compat.20261027.2_amd64.deb
|
||||
sudo apt install ./framebridge-expanded_0.3.2~compat.20261027.3_amd64.deb
|
||||
fb connect
|
||||
~~~
|
||||
|
||||
|
||||
Reference in new issue
Block a user