Glossary
Glossary
| Term | Meaning here |
|---|---|
| ACME | Protocol used to request and renew TLS certificates automatically |
| Ansible | Host-configuration and deployment automation |
| Container | Isolated application process sharing the host kernel |
| Gitea Actions runner | Process that accepts workflow jobs; runner scope and labels define which repositories and job classes it may serve |
| Dataset | Independently configurable ZFS filesystem within a pool |
| Docker Compose | Description and lifecycle tool for related containers on one host |
| Ingress | Shared entry point that routes requests to applications |
| K3s | Lightweight Kubernetes distribution used for selected web workloads |
| Mirror vdev | Two disks storing the same ZFS data for redundancy |
| NAS | Network-attached storage; here, the TrueNAS system |
| OpenTofu | Infrastructure-as-code tool used to define Proxmox VMs |
| RPO | Recovery-point objective: the acceptable amount of lost recent data |
| RTO | Recovery-time objective: the acceptable time to restore a service |
| Rootless Docker-in-Docker | Nested Docker daemon used for isolated builds without mounting the host Docker socket |
| Snapshot | Read-only point-in-time view of a ZFS dataset |
| SOPS | Tool used to keep secret values encrypted in the operations repository |
| Split-horizon DNS | Different DNS answers for private clients and the public internet |
| vdev | ZFS building block; pool reliability depends on every top-level vdev |
| Virtual machine | Software-defined computer with its own operating system |
| WireGuard | Encrypted tunnel used for private remote access |
| ZFS pool | Storage assembled from one or more vdevs and divided into datasets |