Reviewed configuration examples
These are selected files from the environment, adapted for public review. The repository is the single source for the example files; this page explains what they demonstrate and where their evidence ends.
Web hosting and delivery
| Example | What it demonstrates |
|---|---|
| Public nginx backend | A separate static document root, specific listener and connector-source restriction |
| Documentation image proxy | A loopback image backend and separate page/asset cache policies |
| Image build and SSH delivery | Revision-labelled images, serialized jobs and transfer to a restricted receiver |
The public site was initially released by transferring its separate static build. The private image-delivery workflow is not presented as an established public-site release pipeline. The public workflow example lives outside the active workflow directory and has not itself been executed as a public deployment job.
Service configuration
- Runner: non-root service account, credential-file reference and Docker group drop-in. Docker engine access remains highly privileged.
- Private Nextcloud and secondary Nextcloud: observed PHP cron services and five-minute timers. File presence does not prove execution.
- Tailscale: saved forwarding configuration, without VPN identity or authentication state.
- Caddy proxy: an import and its routing template, with private and interface addresses replaced.
- NetBird-related Caddy: DNS ACME environment references and separate routing handlers. Saved Caddy routes do not prove that the public tunnel currently uses Caddy.
- Miniflux: selected listener settings and a database credential-file reference, not the secret.
Reading the examples safely
.example files are reference fragments. .template files contain explicit
placeholders. Neither suffix means the file is a complete or tested deployment
procedure. Do not copy these over a live configuration without adapting,
backing up and validating the intended change.
The Ansible template example remains deferred until its actual source can be reviewed. No generated example is invented to imply that this work is finished.