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).
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -219,3 +219,22 @@ vnox-gateway --config /etc/vnox/config.toml --check
|
|||
```
|
||||
|
||||
Exits 0 if config is valid, prints errors otherwise.
|
||||
|
||||
## Mandatory Central account admission (LNEx v4)
|
||||
|
||||
Every gateway connection needs a short-lived Central account proof, signed by the
|
||||
explicitly configured issuer and bound to the client Ed25519 identity. Private mode
|
||||
uses the same requirement. There is no anonymous admission switch. Configure the
|
||||
public issuer identity obtained through your trusted Central operator:
|
||||
|
||||
```toml
|
||||
[gateway.central_account]
|
||||
issuer = "<Central issuer UUID>"
|
||||
public_key = "<64-character Ed25519 public key hex>"
|
||||
```
|
||||
|
||||
Missing or invalid trust rejects all account admissions. The gateway never accepts
|
||||
a trust key from a client and never automatically discovers issuer keys over HTTP.
|
||||
Central device logout/revocation prevents further proof refresh; previously issued
|
||||
proofs remain valid for at most ten minutes. Active session lifetime follows the
|
||||
existing gateway session policy. See [proof format](../02-protocol/central-account.md).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue