20260914 强制 TOML 配置并完善 TA 刷新与 daemon
Some checks failed
ci / rust (push) Has been cancelled
ci / docker (push) Has been cancelled
ci / audit (push) Has been cancelled

This commit is contained in:
2026-09-14 16:58:08 +08:00
parent 6383e2c12c
commit 4975128945
48 changed files with 2795 additions and 1459 deletions

24
docker/examples/README.md Normal file
View File

@@ -0,0 +1,24 @@
# Container TOML examples
Copy the appropriate TOML outside this directory and point CONFIG_FILE at the
absolute copy path. See [Docker and Compose](../../docs/docker.md) for mounts,
startup, graceful stop and config reload.
| File | Mode | Inputs |
| --- | --- | --- |
| validate.toml | Single run | /input/anchor.tal |
| validate-all5.toml | Single run | Five named RIR TALs |
| daemon.toml | Continuous | /input/anchor.tal |
| daemon-all5.toml | Continuous | Five named RIR TALs |
All examples use text/info diagnostics, require-complete=true, and automatic
TA certificate refresh (ta omitted). TAL files are never automatically updated.
Uncomment an anchor's ta field to use a fixed certificate. Policy
allow-valid-cache permits only a validated cached certificate and marks fallback
partial. First automatic use needs reachable TAL URIs; fixed files are not an
automatic-cache seed. These examples contain no TALs or certificates.
Container paths differ from native configuration paths. Validate uses
/state/repository and /state/repository.ta-cache under the writable /state mount;
daemon uses /data/state and /data/state.ta-cache. Existing /state databases need
an explicit migration or separate cache mount before switching to these paths.