How jaromaz/stws works
Main Components
a) Client Layer:
• Web Browser (entry point)
• noVNC Client (HTML5/JavaScript-based VNC client)
b) Container Layer:
• Docker Container
• Components inside the container:
• noVNC Server
• Websockify (WebSocket proxy)
• TightVNC Server
• X-Org Server
• SyncTERM (BBS Terminal)
[Web Browser] → [noVNC Client Interface]
• ↓
[Docker Container]
• [noVNC Server + Websockify]
• ↓
• [TightVNC Server]
• ↓
• [X-Org Server]
• ↓
• [SyncTERM]
• ↓
[BBS Servers/Telnet]
Important Elements to Highlight
a) Communication Flows:
• Port 6080 exposure for web access
• WebSocket tunneling of VNC protocol
• X11 display handling
• Telnet connectivity
b) Security Layer:
• Password authentication system
• Docker container isolation
Technical Details
• Protocol transitions:
• HTTP/WebSocket (Browser to noVNC)
• VNC protocol (noVNC to TightVNC)
• X11 protocol (TightVNC to X-Org)
• Telnet (SyncTERM to BBS)
Component Descriptions
• noVNC: HTML5 VNC client implementation
• Websockify: WebSocket to TCP proxy
• TightVNC: VNC server implementation
• X-Org: X Window System server
• SyncTERM: BBS terminal emulator
This architecture represents a unique combination of modern web technologies (noVNC, WebSocket) with traditional terminal services (VNC, X11, Telnet), all orchestrated within a Docker container for easy deployment and isolation.