You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TASK.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# TASKS
2
-
- 2026-03-01: DONE. Add a remote launcher script that installs the backend from local source, installs npm when needed, and starts the API plus UI.
2
+
- 2026-03-01: DONE. Add a remote launcher script that installs the backend from local source, installs npm when needed, and starts the API plus UI with the WebSocket URL derived from the API URL by default.
3
3
- 2026-03-01: DONE. Add remote access documentation for LAN and public IP RCH deployments.
4
4
- 2026-02-26: DONE. Add LXMF outbound delivery acknowledgement handling and log recipient delivery confirmations to the event feed.
5
5
- 2026-02-26: DONE. Abort gateway startup when API host/port is already bound to prevent duplicate hub instances and ratchet contention.
Copy file name to clipboardExpand all lines: docs/remoteAccess.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ This guide explains how to reach a Reticulum Community Hub (RCH) instance from a
7
7
-`rch start` is intended for local desktop use and binds the API to `127.0.0.1`.
8
8
- For LAN or WAN access, run the gateway directly with `--api-host 0.0.0.0` (or another reachable interface).
9
9
- For a single-command launcher that installs the backend from local source into a venv and starts both services, run `./run_server_ui_remote.sh`.
10
+
-`run_server_ui_remote.sh` only preconfigures the REST base URL by default; the UI derives the WebSocket URL from that value unless you explicitly set `VITE_RTH_WS_BASE_URL`.
10
11
- Remote clients must authenticate with `RTH_API_KEY`.
11
12
- Remote requests can use either `X-API-Key: <key>` or `Authorization: Bearer <key>`.
12
13
- If the hub is reachable over the public internet, prefer a VPN or HTTPS/WSS behind a reverse proxy.
0 commit comments