Self-hosting
Pointing apps at it
One address to change.
The apps are the normal builds. Only one thing changes: which service they talk to.
What to set
| Setting | What it is |
|---|---|
| Control-plane address | Where accounts, computers and introductions live |
| Coordinator address | Worked out from the above, unless you split them |
| Relay address | Same |
Set them before signing in. Accounts live in the service, so an app pointed elsewhere sees a different world.
Exact keys: settings reference.
Per system
sudo nano /etc/realframe/host.env # system service
nano ~/.config/realframe/host.env # per user
systemctl --user restart realframe-hostDid it work?
Sign in and open Settings in your dashboard. It names the service it is talking to and says whether it is reachable.
Moving an existing fleet
A computer is linked to one service at a time.
Test the new one
With one computer and one app.
Re-link each machine
Point it at the new service, then use a fresh claim code.
Expect them to re-pin
Remembered pairings do not move with the account. Each pair re-pins silently on its first connection against the new service.