User requested a checkpoint and stopped all agents. Deployed artifacts remain the last verified releases; unfinished settings/categories/forums are preserved as WIP. See TODO/roadmap for verification and remaining release/updater work. |
||
|---|---|---|
| .. | ||
| configuration.md | ||
| deployment.md | ||
| operations.md | ||
| README.md | ||
Server / Gateway
A VNOX node contains two components:
gateway — TCP, handles auth / chat / channels / permissions
voice-node — UDP, handles voice relay
Both are written in Rust. Run vnox-serverd for working voice: it connects the
gateway to voice-node through an in-process authenticated credential bridge.
Standalone gateway and voice-node binaries exist, but separate-process signaling
is not implemented; standalone voice-node fails closed without credentials.
The optional central account service is vnox-hub. It provides browser sign-in,
profile/handle selection and own-avatar APIs; it does not relay community messages
or voice. See Hub setup and account API.
Minimum requirements
| Minimum | Recommended | |
|---|---|---|
| CPU | 1 core | 2+ cores |
| RAM | 256 MB | 512 MB |
| Bandwidth | 1 Mbps up | 10 Mbps up |
| OS | Linux x86_64 | Linux x86_64 |
| Ports | TCP 7600, UDP 7700 | configurable |
Voice bandwidth scales with concurrent speakers: ~64 kbps per active speaker (default 64k bitrate, 20ms frames).
Sections
- deployment.md — how to install and run a node
- configuration.md — full config.toml reference
- operations.md — metrics, logs, backup, upgrades