Reset history to current sanitized state
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# Technitium
|
||||
|
||||
Self-hosted authoritative and recursive DNS server for LAN, host-local, and WireGuard clients.
|
||||
|
||||
## Deployment layout
|
||||
|
||||
- **Compose:** `/srv/docker/technitium/docker-compose.yml`
|
||||
- **Static configuration/source:** no additional static configuration or build source
|
||||
- **Non-secret environment:** server domain, recursion policy and network ACL, and upstream DNS-over-HTTPS forwarding
|
||||
are declared inline in Compose; there is no project-local `.env`
|
||||
- **Secrets:** `/srv/docker/secrets/technitium/.env`
|
||||
- **NVMe application state:** `/srv/appdata/technitium/config`
|
||||
- **Bulk HDD data:** none
|
||||
- **Other mounts:** none
|
||||
|
||||
Secrets are never committed to this repository. The central secret environment
|
||||
is supplied to the Technitium DNS Server service.
|
||||
|
||||
## Dependencies and recovery
|
||||
|
||||
- **Networks/dependencies:** external `npm_proxy` network at `192.168.96.42`; DNS is published on loopback, LAN
|
||||
address `192.168.1.3`, and WireGuard address `10.7.0.4`, while the web console is published on LAN TCP port `5380`
|
||||
- **Back up:** `/srv/appdata/technitium/config` and the separately protected Technitium secret environment
|
||||
- **Re-creatable:** the Technitium container; no separate cache or temporary-data mount is declared
|
||||
Reference in New Issue
Block a user