Commit graph

33 commits

Author SHA1 Message Date
a746ec50cd
rm depends_on 2025-04-13 21:53:18 +02:00
6a105c2fce
null_resource -> terraform_data 2025-04-13 21:44:14 +02:00
c91361e7d5
update peertube vm 2025-04-13 21:42:46 +02:00
6a4eb90658
in-source tf deployment logic 2025-04-13 21:14:33 +02:00
1f5977468c
ditch hermetic to simplify - still gets infinite recursion 2025-04-13 13:36:04 +02:00
9f689faa32
special_args -> nix_path + module 2025-04-13 13:16:57 +02:00
ef214ced10
merge tf modules 2025-04-13 13:11:04 +02:00
d955e39f4c
simplify tf 2025-04-12 22:18:21 +02:00
3418d0e76d
get terraform-nixos working deployed 2025-04-12 22:11:23 +02:00
81011d0062
pass deploy env vars thru 2025-04-12 12:31:47 +02:00
8a50680b9f
document dev process 2025-04-10 14:01:07 +02:00
4f83f51e17
rm .auto.tfvars.json, as the local ssh key and socket are not relevant deployed 2025-04-10 10:07:30 +02:00
ce0e8e39f2
un-track .terraform 2025-04-10 09:03:58 +02:00
1da2e9e497
special-args -> hermetic 2025-04-10 09:00:21 +02:00
79e58e21f4
nixos-anywhere -> terraform-nixos
intended to swap out nixos-anywhere for terraform-nixos, over:

- don't need nixos-anywhere to install nixos; we preload nixos to VMs
- [awkward non-flake
usage](https://nix-community.github.io/nixos-anywhere/howtos/use-without-flakes.html#3-set-nixos-version-to-use)
-  seemed not to pick up on config changes, as observed by test VMs
losing their panel keys after TF sync

however, it seems that terraform-nixos has its own flaws:

- its output using a random id, i.e. forcing to push even on no changes
- so far did not get ssh authentication to work
2025-04-09 17:05:00 +02:00
2b0ee4e52d
add ssh key to not need root user 2025-04-09 17:05:00 +02:00
551e860b5b
use root user as in #301 - given #297 seems to actually deploy! 2025-04-09 17:04:53 +02:00
3270cc89e7
update mastodon host 2025-04-09 17:04:33 +02:00
c93f16bcb2
change ssh user to root 2025-04-09 17:04:33 +02:00
76e0594956
for now gitignore .auto.tfvars.json used to track TF module of nixos-anywhere
in case we want that file for something else, we can move this (and its
ignore) to something separate.
2025-04-09 17:04:33 +02:00
0350f68427
untrack TF generated provider/module stuff - local dev now requires following launch/README.md 2025-04-09 17:04:33 +02:00
fc4fc60982
update nixos-anywhere to fix error 'installable ... does not correspond to a Nix language value' 2025-04-09 17:04:15 +02:00
b4a65169c6
rm launch flake, as i seem to have reached similar progress without it 2025-04-09 17:04:07 +02:00
29664fef8c
get TF in prod to the same 'installable ... does not correspond to a Nix language value' for non-flakes
seemingly gets further when a similar command is tried from terminal.
as per https://github.com/NixOS/nix/issues/8752#issuecomment-1694714693,
this may have to do with aligning the current working directory.
2025-04-09 17:04:07 +02:00
195a8d4de8
document updating TF module 2025-04-09 17:03:43 +02:00
727b62f588
update 2025-04-09 17:03:43 +02:00
b3e783d4a5
move tf init out of python over read-only nix env 2025-04-09 17:03:43 +02:00
c1aa71e319
properly pass repo dir for prod, be it with hard-coded TF init 2025-04-09 17:03:43 +02:00
817c724557
use flake-sourced nixos-anywhere in tf, to reproduce modules for nix 2025-04-09 17:00:20 +02:00
d599d5b640
switch launch shell to root flake's nixpkgs, see #279 2025-04-09 17:00:20 +02:00
be03794f5f
make re-exports explicit again 2025-04-09 17:00:20 +02:00
3eb6d93216
tf 2025-04-09 17:00:20 +02:00
f947e17d96
allow accessing test vms from fedi201's machine ssh key, closes #286 2025-04-09 17:00:01 +02:00