111b23b94b
First runnable kez-chat-server binary plus its docker-compose deploy
recipe. Implements steps 2-3 of the document.md sequenced plan; the
rust-lib refactor (step 1) is deferred — chat-server path-deps on
rust/crates/kez-core for now, which works and matches what
rust-sig-server already does.
What's in this commit:
kez-core (1-line change)
- New public `verify_envelope<T>(payload, signature)` helper that
dispatches Schnorr / Ed25519 / future suites by signature.alg.
Used by chat-server's registration verifier; downstream value
beyond chat-server too.
kez-chat-server (new crate)
- src/main.rs: tokio + axum + tracing entry; clap config; graceful
Ctrl-C shutdown.
- src/lib.rs: re-exports so tests can drive the same router.
- src/config.rs: env/flag config (bind, db, server, sig_server_url,
web_dir) with defaults sane for both dev and prod.
- src/error.rs: typed ApiError → structured JSON responses with
stable error codes.
- src/store.rs: SQLite-backed handle registry, UNIQUE on both
(handle) and (primary_id); race-safe via SQL primary key.
- src/handles.rs: username validation (length, charset, reserved
list, must start with letter/digit).
- src/registration.rs: SignedRegistration envelope sharing KEZ's
JCS canonical-bytes pattern; signature verification via the new
kez-core helper; replay protection via ±5-minute clock skew check.
- src/api.rs: all six routes in one file —
GET /v1/healthz
GET /v1/u/:handle
POST /v1/register
GET /.well-known/webfinger
POST /internal/nats/auth (501 stub for v0.1; wired up in v0.2)
GET / (placeholder HTML; ServeDir when web/dist exists)
tests/http.rs — 13 integration tests
- Stands up the real router on a random port; uses reqwest.
- Coverage: healthz, lookup-404, full register→lookup round-trip,
duplicate-handle conflict, wrong-server rejection, reserved-name
rejection, tampered-signature rejection, stale-timestamp rejection,
WebFinger success + wrong-server-404, placeholder SPA renders,
NATS callout 501, JCS determinism sanity.
deploy/
- Dockerfile: multi-stage build (rust:1.86-slim → debian:bookworm-slim).
Build context is repo root so the path dep on kez-core resolves.
Runtime image ~50 MB; runs as non-root uid 10001.
- Dockerfile.sig-server: same pattern for the existing
rust-sig-server, so the stack builds from one git pull.
- docker-compose.yml: three services (chat-server + nats + sig-server)
with named volumes for persistence. Ports: 6969 (chat HTTP),
4222/8443/8222 (NATS native/ws/monitoring), 7878 (sig-server).
- nats.conf: WebSocket on 8443 for the browser SPA, JetStream
enabled, auth_callout pointing at chat-server's
/internal/nats/auth endpoint (issuer nkey is a placeholder — must
be replaced with a real one before going live).
README.md
- Documents all endpoints with example bodies.
- Quick-start for both local dev and full Docker compose.
- Honest list of what's in v0.1 vs what's still stubbed.
Smoke-tested running on 127.0.0.1:6969:
GET /v1/healthz → {"server":"kez.lat","status":"ok","version":"0.1.0"}
GET / → placeholder HTML rendering
GET /v1/u/ghost → 404
POST /internal/nats/auth → 501 with "wired up in v0.2"
cargo test → 13 passed.
cargo build --release → 19.6s, clean.
52 lines
1.8 KiB
Plaintext
52 lines
1.8 KiB
Plaintext
# NATS config for kez-chat home server.
|
|
#
|
|
# - Native NATS protocol on 4222 for CLI clients (TLS terminated by your
|
|
# reverse proxy in production).
|
|
# - WebSocket on 8443 for the browser SPA. Also TLS-terminated upstream.
|
|
# - JetStream on for offline message buffering (durable consumers).
|
|
# - auth_callout points at our chat-server's /internal/nats/auth endpoint.
|
|
# The chat-server is the source of truth for which nkeys are allowed
|
|
# to connect and what subjects they can publish/subscribe to.
|
|
|
|
# Standard NATS listener (CLI clients use this).
|
|
listen: 0.0.0.0:4222
|
|
|
|
# WebSocket listener (browser SPA uses this via nats.ws).
|
|
websocket {
|
|
port: 8443
|
|
no_tls: true # TLS terminated by Cloudflare tunnel / reverse proxy
|
|
}
|
|
|
|
# Persistent storage for durable consumers (offline buffering).
|
|
jetstream {
|
|
store_dir: /data/jetstream
|
|
max_mem: 1G
|
|
max_file: 10G
|
|
}
|
|
|
|
# Monitoring / healthcheck.
|
|
http_port: 8222
|
|
|
|
# Auth callout: every connection's auth request is forwarded to our
|
|
# chat-server, which checks the handle registry and signs a response.
|
|
# Until we ship the v0.2 auth callout, the chat-server returns 501 and
|
|
# all connections are rejected. That's intentional — fail closed.
|
|
authorization {
|
|
auth_callout {
|
|
# The chat-server signs its callout responses with this nkey; NATS
|
|
# accepts responses signed by this key only. Generated once via
|
|
# `nsc generate nkey -o` (operator-level) and embedded in the
|
|
# chat-server's deployment secrets.
|
|
#
|
|
# PLACEHOLDER — replace before going live.
|
|
issuer: "ABACVOI4POPS3SBFLDQYTQHHHACRVMCM2HK7PXX4UTI7XYWQHQGOA3PX"
|
|
|
|
# NATS uses this user identity when invoking the callout endpoint.
|
|
# Distinct from real users; it's just an internal protocol marker.
|
|
auth_users: ["AUTHUSER"]
|
|
|
|
# The account real users land in once the callout approves them.
|
|
account: "DEFAULT"
|
|
}
|
|
}
|