chore: rename quicproquo → quicprochat in docs, Docker, CI, and packaging
Rename all project references from quicproquo/qpq to quicprochat/qpc across documentation, Docker configuration, CI workflows, packaging scripts, operational configs, and build tooling. - Docker: crate paths, binary names, user/group, data dirs, env vars - CI: workflow crate references, binary names, artifact names - Docs: all markdown files under docs/, SDK READMEs, book.toml - Packaging: OpenWrt Makefile, init script, UCI config (file renames) - Scripts: justfile, dev-shell, screenshot, cross-compile, ai_team - Operations: Prometheus config, alert rules, Grafana dashboard - Config: .env.example (QPQ_* → QPC_*), CODEOWNERS paths - Top-level: README, CONTRIBUTING, ROADMAP, CLAUDE.md
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Service Architecture
|
||||
|
||||
The quicproquo server exposes 44 RPC methods through a single QUIC + TLS 1.3
|
||||
The quicprochat server exposes 44 RPC methods through a single QUIC + TLS 1.3
|
||||
endpoint on **port 5001**. Methods are dispatched by numeric method ID using
|
||||
the v2 Protobuf framing protocol. This page documents the method reference,
|
||||
connection lifecycle, storage model, and authentication flow.
|
||||
@@ -10,11 +10,11 @@ connection lifecycle, storage model, and authentication flow.
|
||||
## RPC Endpoint
|
||||
|
||||
A single QUIC + TLS 1.3 listener on **port 5001** serves all operations.
|
||||
The ALPN identifier is `qpq`. Each RPC call uses a dedicated QUIC
|
||||
The ALPN identifier is `qpc`. Each RPC call uses a dedicated QUIC
|
||||
bidirectional stream; calls are concurrent and do not block each other.
|
||||
|
||||
```text
|
||||
quicproquo-server (port 5001, ALPN: "qpq")
|
||||
quicprochat-server (port 5001, ALPN: "qpc")
|
||||
|
|
||||
+-- Auth (100-103)
|
||||
| +-- 100: OpaqueRegisterStart
|
||||
@@ -243,7 +243,7 @@ Client Server
|
||||
2. <- QUIC HANDSHAKE
|
||||
TLS 1.3 ServerHello +
|
||||
Certificate (self-signed)
|
||||
ALPN: "qpq"
|
||||
ALPN: "qpc"
|
||||
|
||||
3. Client verifies server cert against
|
||||
pinned CA cert (--ca-cert flag)
|
||||
@@ -345,10 +345,10 @@ validates it on every authenticated method call.
|
||||
|
||||
| Flag | Env var | Default | Description |
|
||||
|----------------|----------------------------|------------------------|-------------|
|
||||
| `--listen` | `QPQ_LISTEN` | `0.0.0.0:5001` | QUIC listen address (host:port). |
|
||||
| `--data-dir` | `QPQ_DATA_DIR` | `data` | Directory for persisted state. |
|
||||
| `--tls-cert` | `QPQ_TLS_CERT` | `data/server-cert.der` | Path to TLS certificate (DER). Auto-generated if missing. |
|
||||
| `--tls-key` | `QPQ_TLS_KEY` | `data/server-key.der` | Path to TLS private key (DER). Auto-generated if missing. |
|
||||
| `--listen` | `QPC_LISTEN` | `0.0.0.0:5001` | QUIC listen address (host:port). |
|
||||
| `--data-dir` | `QPC_DATA_DIR` | `data` | Directory for persisted state. |
|
||||
| `--tls-cert` | `QPC_TLS_CERT` | `data/server-cert.der` | Path to TLS certificate (DER). Auto-generated if missing. |
|
||||
| `--tls-key` | `QPC_TLS_KEY` | `data/server-key.der` | Path to TLS private key (DER). Auto-generated if missing. |
|
||||
|
||||
Logging level is controlled by the `RUST_LOG` environment variable (default: `info`).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user