rmancinas/remote-control-support-webapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8 Commits 1 Branch 0 Tags
main
Commit Graph
2 Commits
Author SHA1 Message Date
rmancinasandClaude Opus 5 30feb5f61b fix(deploy): publish on 5910, 8091 is taken on the Swarm ingress
Build and Deploy Remote Control Support / Test (push) Successful in 11s
Details
Build and Deploy Remote Control Support / Build Image (push) Successful in 47s
Details
Build and Deploy Remote Control Support / Deploy to Portainer (push) Successful in 9s
Details 
The first real deploy failed with "port '8091' is already in use by
service 'ai-training-lab_ai-lab' as an ingress port". Worth noting the
port answered nothing when probed over HTTP — a Swarm ingress
reservation survives the service behind it being down, so probing is not
a way to find a free port.

5910 is VNC display :10 and sits clear of the 809x web-app block.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-11 23:52:48 -07:00
rmancinasandClaude Opus 5 999717f77b feat: self-hosted remote support over VNC 
Browser-based remote control (noVNC) with invite links, per-user access
control, garagedoor SSO and a persisted client list.

The hub proxies RFB rather than pointing the browser at a VNC server. That
is what lets it authenticate upstream with a stored password the browser
never sees, and enforce view-only by dropping input messages on the
client->server stream instead of hiding buttons.

Machines are reachable two ways: direct TCP for LAN hosts, or an outbound
agent tunnel for anything behind NAT. Node 22's global WebSocket keeps the
agent dependency-free, and node:sqlite keeps the image free of native
builds.

Ships with an end-to-end suite that boots the real server against a fake
VNC server and a fake auth service (72 assertions), plus Gitea Actions
CI/CD to Portainer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
 2026-08-11 23:37:35 -07:00