aboutsummaryrefslogtreecommitdiff
path: root/infra (follow)
Commit message (Collapse)AuthorAgeFilesLines
* manage terraform configuration with terranixFranck Cuny2025-08-3117-634/+0
| | | | | | | | | All the terraform configuration is managed within one state instead of having multiple state for each components. This might not be the best practice but it simplifies things for me. Now, all I need to do is to run `nix run .#tf -- plan` and I can see what will be changed for all the resources that I care about.
* run `goget` on `go.fcuny.net`Franck Cuny2025-08-241-0/+9
|
* initial setup for forgejo and caddyFranck Cuny2025-08-121-0/+18
|
* add a script to apply DNS terraformFranck Cuny2025-08-121-0/+7
|
* update a few .envrcFranck Cuny2025-08-101-0/+12
|
* manage a DigitalOcean virtual machine with nixosFranck Cuny2025-08-106-9/+174
| | | | | | | Add a new machine on DigitalOcean and provision it using terraform + nixos-anywhere. This takes care of bringing the machine up on nixos completely, and use a static SSH host key in order to configure wireguard at the same time.
* write the terraform configuration in HCLFranck Cuny2025-08-0913-180/+423
| | | | | | This will become more tricky over time. Using HCL is not as elegant and forces me to learn yet another DSL, but this will be easier to debug if I'm stuck with something I don't know how to do.
* move all profiles, modules, and flakes to top-levelFranck Cuny2025-07-212-0/+180