Archived
beatzaplentyandClaude Sonnet 4.6
f85c65870f
Consolidates nixos, docker, raspi, and debian-configuration into a single infrastructure-as-code repo. Includes: - ansible/: full inventory + proxmox-hardening, freeipa, and raspberrypi roles (converted from debian-configuration bash scripts) - terraform/: Proxmox VMs, Dynu DNS, Pi-hole (decommissioned stub), Docker container catalog — migrated from docker/infrastructure/terraform/ - stacks/docker/, stacks/raspi/, nixos/: placeholder READMEs pending git subtree population (see implementation plan) - docs/: internal MkDocs site with architecture, network topology, runbooks, and drift-detection guide; external sanitized site - scripts/: drift-detect.sh, docs-build.sh, install-hooks.sh, check-secrets.sh - CI: secret-scan (push/PR), drift-detect (daily), docs-build (on change) - Pi-hole removed throughout — DNS is FreeIPA, DHCP is router See docs/internal/implementation-plan.md for the phased rollout after pushing to Gitea. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UvNjoxTWEDkhXsd1Dq2ETP
Terraform Proxmox Inventory Layer
This directory codifies existing Proxmox infrastructure using an import-first reconciliation model.
Purpose
- Track existing Proxmox VMs in Terraform.
- Reconcile imported VM configuration into maintainable, explicit files.
- Represent physical host metadata as structured Terraform locals/outputs.
- Support documentation inventory and future downstream tooling.
Current repository status
This directory already contains imported/reconciled VM resources (for example docker, server-nixos, nix-cache, pbs, pihole) plus host metadata locals/outputs.
This means it is no longer just a scaffold; treat it as active infrastructure inventory code.
Workflow standard (brownfield)
- Import one existing VM at a time.
- Confirm provider-specific import ID format.
- Inspect state/plan details.
- Keep hand-maintained
.tffiles focused and readable. - Use
ignore_changesonly where drift noise is unavoidable. - Stop when plan is sane/no-op for intended scope.
File organization expectations
- Prefer one-resource-per-file patterns when practical.
- Keep shared metadata in
locals/outputs with clear descriptions. - Keep generated comments/config under ongoing cleanup rather than assuming generated output is final.
Safety notes
- Do not run broad applies casually.
- Do not commit real credentials or
.tfstate*. - Keep changes incremental and reviewable.