snix/ops/hcloud
Florian Klink 9e7cadeded fix(ops): delete email config for now
We don't have an email server configured (yet), we can resurrect it once
we do.

Change-Id: I568075154c6169d031462f39b43ce5897a754f19
Reviewed-on: https://cl.snix.dev/c/snix/+/30109
Autosubmit: Florian Klink <flokli@flokli.de>
Tested-by: besadii
Reviewed-by: Ilan Joselevich <personal@ilanjoselevich.com>
2025-03-18 21:52:06 +00:00
..
.gitignore feat(*): initialize new Snix infrastructure 2025-03-17 17:15:07 +00:00
default.nix feat(*): initialize new Snix infrastructure 2025-03-17 17:15:07 +00:00
raito.pub feat(*): initialize new Snix infrastructure 2025-03-17 17:15:07 +00:00
README.md feat(*): initialize new Snix infrastructure 2025-03-17 17:15:07 +00:00
snix.tf fix(ops): delete email config for now 2025-03-18 21:52:06 +00:00

Hetzner cloud configuration

This contains Terraform configuration for setting up our Hetzner cloud resources, except S3, see //ops//hetzner-s3 for this.

Through //tools/depot-deps a tf-hcloud binary is made available which contains a Terraform binary pre-configured with the correct providers. This is automatically on your $PATH through direnv.

However, secrets still need to be loaded to access the Terraform state and speak to the Hetzner API. These are available to certain users through //ops/secrets.

This can be done with separate direnv configuration, for example:

# //ops/buildkite/.envrc
source_up
eval $(age --decrypt -i ~/.ssh/id_ed25519 $(git rev-parse --show-toplevel)/ops/secrets/tf-hcloud.age)