Skip to main content
  1. pages/

Home Lab: Services & Software

·252 words·2 mins·
Table of Contents
Home Lab - This article is part of a series.
Part 5: This Article
Note

This is a living document, and is subject to change at any given time.

Last updated August 5th, 2026.

Everything below except the “Not Managed by Dojo” section is deployed and configured from the Dojo Ansible monorepo, see How I GitOps’ed My Homelab.

Services
#

ServiceDeployment MethodDescription
Knot DNSVM pair (knot-1/2)Authoritative DNS, behind keepalived VIP
CoreDNSVM pair (coredns-1/2)Client-facing resolver, behind keepalived VIP
Pi-HoleContainer pair (ctr-core-2/3)Ad blocking, kept in sync via Nebula-sync
Caddy 2Container (ctr-core-1)Reverse proxy, automatic wildcard TLS via Cloudflare DNS-01
DMZ CaddyContainer (ctr-dmz-1)Second, fully separate reverse proxy for genuinely public services
cloudflaredContainer (ctr-core-1)Cloudflare Tunnel for internal services that need external reach
GitHub Actions runnerVM (ghr-1)Self-hosted CI runner for all Dojo deployments
DocsiteStatic site, served by CaddyAuto-generated docs dashboard
Ansible control VMVMHolds the Dojo checkout and secrets
Home AssistantVM (hand-built, not Dojo-managed)Home automation
PlexVM (hand-built, not Dojo-managed)Media server, Intel Arc SR-IOV hardware transcoding
TautulliContainer on SynologyPlex monitoring
DHCPUniFiIP assignment
VPNUniFiRemote network access

Not Managed by Dojo
#

Home Assistant and Plex both moved onto the new Proxmox VE cluster as hand-built appliance VMs, outside Ansible’s reach. Plex gets OS patching only, through a bare inventory entry in the maintenance role; Home Assistant does not even get that. Plex uses Intel Arc SR-IOV passthrough for hardware transcoding, see Intel Arc SR-IOV Hardware Transcoding with Plex on Proxmox VE for the full setup.

Home Lab - This article is part of a series.
Part 5: This Article

Related