Infrastructure

Terraform modules for Proxmox, AWS disaster recovery, Bedrock agents, static sites, and self-hosted GitHub Actions runners.

Provision once with Terraform, configure with Ansible, run forever.

The infrastructure layer is Terraform-managed. Every module is opinionated about deployment shape: LXC for production homelab workloads, Docker on a dedicated VM only when vendor-locked, AWS for disaster recovery and managed services.

The Proxmox stack

Terraform builds VMs and LXCs (coral). Ansible takes the inventory and configures hosts (green), then deploys the app stack on top.

AWS module map

Repo	Purpose
terraform-aws	Splunk DR footprint — cold capacity for failover
terraform-runs-on	Self-hosted GitHub Actions runners on AWS spot instances
tf-splunk-aws	Cost-optimised Splunk deployment on AWS

Repos in this section

terraform-proxmox

VMs and LXC containers on the Proxmox cluster.

ansible-proxmox

Host config — ZFS, networking, users, hardening.

ansible-proxmox-apps

App deploy — HAProxy, Cribl Edge, Cribl Stream.

terraform-aws

AWS DR footprint for Splunk failover. Cold infra, ready to go warm.

CI/CD

GitHub Actions strategy: self-hosted RunsOn AWS spot, OIDC, plan/apply pattern.

orbstack-kubernetes

Local Kubernetes cluster on macOS — monitoring stack + AI gateway.

tf-splunk-aws

Cost-optimized Splunk deployment on AWS.

Cross-cutting topics

Kubernetes overview

OrbStack as the local control plane; what runs on K8s vs LXC vs Docker.

LXC vs Docker

The four-question decision tree for every new workload.

SOPS for IaC

Encrypted-at-rest secrets across Terraform and Ansible repos.

Deployment philosophy

LXC is the default for production homelab services. Native packages where possible. Docker only when a vendor ships Docker-only images and there’s no native path — and only on a dedicated docker-host VM so high-volume network traffic never crosses Docker’s virtualized network stack.

For configuration of provisioned hosts, see Configuration.