Repository navigation
0.8.0
Highlights
Remote access from anywhere. Reach your server from any browser in the world, with no port to open on your router and no VPN. Set REMOTE_ENABLED=true and REMOTE_URL, and the server prints a link at startup. The browser and the server talk over a WebRTC data channel, encrypted end to end, directly when the networks allow it and through a TURN relay when they do not. The connection badge in the header shows which of the two carries it.
- The link pins your server. The instance id derives from the server's certificate, and the page refuses any server that does not present it, so not even the signaling server can stand in for yours.
- The token stays between the browser and your server. The browser proves it holds the access token with a code bound to its own certificate before the server spends anything on it; the signaling server relays it without learning the token. Wrong proofs back off per address.
- The signaling server stores nothing. Hosts and sessions live in memory only, and it never sees your conversations.
- Self-hosting.
packages/p2p-server(signaling server and hosted web app) anddeploy/coturn(TURN relay) come with Dockerfiles, CapRover definitions and a deployment guide: docs/remote-access.md.
Public signaling server. https://arc-p2p-server.arc.douglasjunior.work is available for anyone to use at their own risk, as is and without warranty. Using it means trusting its operator with the page that reads your access token; read the disclaimer or host your own.
Upgrade notes
- Remote access is off by default. Turning it on requires
REMOTE_URL(HTTPS, or HTTP only forlocalhost) and an access token of at least 32 characters; leaveWEB_ACCESS_TOKENempty to use the generated one. - The certificate and key that identify the server live in
DATA_DIR/remote; keep that folder to keep the same link across restarts.
New settings in .env.example: REMOTE_ENABLED and REMOTE_URL. The signaling server and the relay read P2P_* and TURN_* variables, described in the deployment guide.
What's Changed
- feat: reach the server from anywhere over WebRTC by @douglasjunior in #24
Full Changelog: 0.7.0...0.8.0