On: Ask HN: Can any Hetzner user please explain your w...

[sshine]

I provision a single VPS that acts as Terraform & Ansible control:

  - Store and run Terraform setup in git
  - Store and distribute SSH keys
  - Store and run Ansible scripts for bootstrapping (e.g. Kubernetes clusters on dedicated, or more VPS'es)
  - Host VPN and some low-intensity services (I'd delegate both of these if I had a bigger budget)

Specifically, this replaces the use of Terraform Cloud.

I enjoyed using Terraform Cloud for a more cloudy setup with easy GitHub pull-request integration at a past employer.

But I'm specifically aiming for simplicity here. It doesn't scale as well to a team of 2+ without establishing conventions.

I haven't explored what self-hosted alternatives there are to Terraform Cloud.

[dinkleberg → sshine]

Have you tried using one of the different terraform backends? I usually have mine backed to a gcs bucket so I can run terraform from a CI job and have it maintain state correctly.

[sshine → dinkleberg]

I have only experimented, but I haven't settled on anything.

I actually like having my Terraform single source of truth in local git (backed up).

What I'm missing from Terraform Cloud is the `terraform plan` on pull-request submission and `terraform apply` upon merge.

I might do that with ArgoCD. And better CI/CD integration in Forgejo. But that's a long shot still.