openvibers/openvibe.link Commits

Docs: pair from openvibe.link/pair and see your machines at openvibe.link/machines (#135)

OP OpenVibers committed 5 days ago · 3f8970cd96 · 2 files, +16 −2

The install guide and the README now send people to Link's own signed-in machines hub for the pairing code and the
machine list, while openvibe.bot/machines keeps working. Matches the openvibe.link pages.

Changes

ddiff --git a/README.md b/README.md
iindex 0a13b25..facd997 100644
---- a/README.md
++++ b/README.md
@@@ -115,6 +115,11 @@ tasks this machine ran today, and what happened, and lets you pause everything,
  share a port, or send files (not in this version). It is served only on loopback, with a per-run token in the address
  fragment that every API call must send; see [docs/panel.md](docs/panel.md) for the security rules.
  
++**Your machines:** [openvibe.link/machines](https://openvibe.link/machines) opens the signed-in machines hub: each
++paired machine, whether it is online, the roles it plays (Codes jobs, desks, your own models, a robot), and pairing a
++new one from [openvibe.link/pair](https://openvibe.link/pair). It is the same account page on openvibe.my, reached from
++Link's own name.
++
  **Link on your phone (Android, v0):** the same pairing and connection as desktop Link, in an app: your agents'
  approvals in your pocket (money, passwords, deletions and a send to a new recipient ask for a fingerprint first), the
  Dock's activity read-only, and **Send to OpenVibe** from any app's share sheet to your Download drive. It pairs from
ddiff --git a/docs/install.md b/docs/install.md
iindex c7c1f61..f186d08 100644
---- a/docs/install.md
++++ b/docs/install.md
@@@ -23,7 +23,8 @@ Links for every file are on [openvibe.link](https://openvibe.link/#install); the
     .\openvibe-link install
     ```
  
--   The code comes from [openvibe.bot/machines](https://openvibe.bot/machines) (**Add a machine**).
++   The code comes from [openvibe.link/pair](https://openvibe.link/pair), which signs you in and opens the machines hub
++   (**Pair a machine**); [openvibe.bot/machines](https://openvibe.bot/machines) shows the same code.
  4. `openvibe-link status` shows the link; the machine appears in your account's machines.
  
  `openvibe-node.exe` is the same program under its old name, so an existing shortcut or script keeps working.
@@@ -76,7 +77,8 @@ plugin bundle and `install.sh`; unpack one and run `sudo ./install.sh --local .`
  ### Android (the existing APK)
  
  Download `openvibe-link-<tag>.apk` on the phone, allow installing from that source when Android asks, and open
--**OpenVibe Link**. Pair with a code from [openvibe.bot/link/phone](https://openvibe.bot/link/phone). This is the direct
++**OpenVibe Link**. Pair with a code from [openvibe.link/pair](https://openvibe.link/pair) or
++[openvibe.bot/link/phone](https://openvibe.bot/link/phone). This is the direct
  APK, not Google Play; it has approvals, Activity, pairing and **Send to OpenVibe**, and no phone automation. Details:
  [android.md](android.md).
  
@@@ -141,6 +143,13 @@ made the files, with the name, model, who may drive and Live they chose there, s
  be at the robot. A key adds one robot and lasts 7 days; a retry before the robot has paired pairs the same robot again.
  Its output is in `journalctl -u openvibe-setup` on the Pi.
  
++## Pair from openvibe.link
++
++[openvibe.link/pair](https://openvibe.link/pair) signs you in and opens **Your machines** at openvibe.my: every machine
++you paired with whether it is online, what it is allowed to do, a one-time code and the command to pair another, and
++rename or revoke. The installer asks for that code, so the whole one-minute start is: install, get the code there,
++paste it. Nothing about pairing lives only on openvibe.bot any more; the old page still works.
++
  ## Quick start with a code from openvibe.bot (Linux, Raspberry Pi, macOS)
  
  1. On openvibe.bot, add a robot. You get a code like `ABCD-1234` (valid 10 minutes) and the installer command with