Comment by dml2135

Yup this is what I've got up and running recently and it's been awesome.

My setup is roughly the following.

- Dell optiplex mini running Proxmox for compute. Unraid NAS for storage.

- Debian VM on the Proxmox machine running Forgejo and Komodo for container management.

- Monorepo in Forgejo for the homelab infrastructure. This lets me give Claude access to just the monorepo on my local machine to help me build stuff out, without needing to give it direct access to any of my actual servers.

- Claude helps me build out deployment pipeline for VMs/containers in Forgejo actions, which looks like:

  - Forgejo runner creates NixOS builds => Deploy VMs via Proxmox API => Deploy containers via Komodo API

- I've got separate VMs for

  - gateway for reverse-proxy & authentication

  - monitoring with prometheus/loki/grafana stack

  - general use applications

Since storage is external with NFS shares, I can tear down and rebuild the VMs whenever I need to redeploy something.

All of my docker compose files and nix configs live in the monorepo on Forgejo, so I can use Renovate to keep everything up to date.

Plan files, kanban board, and general documentation live adjacent to Nix and Docker configs in the monorepo, so Claude has all the context it needs to get things done.

I did this because I got tired of using Docker templates on Unraid. They were a great way to get started, but it's hard to pin container versions and still keep them up-to-date (Unraid relies heavily on the `latest` tag). Moving stuff over to this setup bit-by-bit and I've been really enjoying it so far.