chore(server): checkpoint deployed services and unfinished forums
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.
This commit is contained in:
parent
d6d406bbf5
commit
c18ccadf99
96 changed files with 8665 additions and 276 deletions
|
|
@ -1,14 +1,20 @@
|
|||
# Server / Gateway
|
||||
|
||||
A VNOX node consists of two processes:
|
||||
A VNOX node contains two components:
|
||||
|
||||
```
|
||||
gateway — TCP, handles auth / chat / channels / permissions
|
||||
voice-node — UDP, handles voice relay
|
||||
```
|
||||
|
||||
Both are written in Rust. They can run on the same machine or separately.
|
||||
For most self-hosted setups, running both on one machine is fine.
|
||||
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](../../hub/README.md) and [account API](../../hub/AUTH.md).
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue