authorgravatar for julius0216@outlook.comJulius Marminge <julius0216@outlook.com> 2026-04-10 00:43:38-07:00
committergravatar for noreply@github.comGitHub <noreply@github.com> 2026-04-10 07:43:38+00:00
log1a05d8ca1a5ab8d8562eb576bfd473459dcc8ea3
tree1ac59bdd79eba0b39c77e19d2b11bcb68f9fb8b7
parentcf9f236c80aaa8ea4c3827d98362b752759d1ec6
signature Signed by PGP key B5690EEEBB952194

Document remote server network access setup (#1872)

1 files changed, 16 insertions(+), 1 deletions(-)

REMOTE.md+16-1
......@@ -12,7 +12,22 @@ That gives you:
1212- transport security at the network layer
1313- less exposure than opening the server to the public internet
1414
15## Headless Server Flow
15## Enabling Network Access
16
17There are two ways to expose your server for remote connections: from the desktop app or from the CLI.
18
19### Option 1: Desktop App
20
21If you are already running the desktop app and want to make it reachable from other devices:
22
231. Open **Settings** → **Connections**.
242. Under **Manage Local Backend**, toggle **Network access** on. This will restart the app and run the backend on all network interfaces.
253. The settings panel will show the address the server is reachable at (e.g. `http://192.168.x.y:3773`).
264. Use **Create Link** to generate a pairing link you can share with another device.
27
28### Option 2: Headless Server (CLI)
29
30Use this when you want to run the server without a GUI, for example on a remote machine over SSH.
1631
1732Run the server with `t3 serve`.
1833