Document second-machine installation and verification scope

This commit is contained in:
2026-11-08 16:48:57 +00:00
parent 36f73bb89d
commit eea4b1ddc9
@@ -0,0 +1,32 @@
# Installing a second machine
Install the server independently on the Linux computer using the current source
checkout and `./install`. The Linux user needs a logged-in `systemctl --user`
session, Go as pinned in go.mod, Node 18+, Python 3.9+, a C compiler, git, curl,
running Docker, and its own configured OpenCode installation. See ../install.md.
This does not transfer provider credentials or the Mac server database.
On the phone, keep the existing app/data and add the Linux server in Settings →
Servers. Give each logical server a distinct name (for example Mac and Linux).
Add alternative LAN/tailnet addresses as endpoints of the same logical server;
add the second computer as a separate server. Sign in to each machine separately.
The app retains separate credentials and server-scoped navigation/drafts.
New chat asks for the machine before loading that machine's harness choices.
Pipeline, run and chat metadata identifies the selected machine. Lists retain
their existing selected-server context; this release does not aggregate both
machines into a single list.
For a desktop client alone, use `./install --linux --output ./dist` or
`./install --macos --flutter /path/to/flutter --output ./dist`. These commands
build clients without installing a server. Add `--publish` to offer the resulting
platform build from an installed server's authenticated update feed. Android,
Linux and macOS clients check saved machines for compatible updates; desktop
archives are downloaded rather than replacing the running application.
Manager verification before delivery: 53 native-installer regression tests,
15 app-builder tests, and an isolated source lifecycle smoke test passed. The
smoke test used a private HOME/config/database and no model inference. Linux
systemd login startup and installation on the operator's Linux computer remain
for that physical-machine test; successful Docker client compilation does not
verify either. No Android device was connected during this release preparation.