- Feb 10, 2022
-
-
Jean-Paul Calderone authored
morph offers an auto-passed `nodes` parameter from which we can read all of the nodes in the morph "network". We can dig around in this to find the monitoring node and then read its configured IP address. It may be worth noting that this address appears in at least two places in the configuration. It appears in our "input" configuration which grid.nix defines. This change reads it from there. We also have a NixOS module `nixos/modules/monitoring/vpn/server.nix` which reads this "input" and uses it to configure `networking.wireguard.interfaces.monitoringvpn`. This is fed onwards to <nixos> to generate actual system configuration. It seems better to use the former than the latter because we have more direct control over it and if we consider the whole configuration system a function then it is more like an argument we are supplying rather than an obscure implementation detail.
-
- Feb 03, 2022
-
-
Florian Sesser authored
Should be pure refactoring
-
Florian Sesser authored
-
- Jan 31, 2022
-
-
Tom Prince authored
Note that changing the origin repository in the on-node deployment checkout is also required. See https://whetstone.private.storage/privatestorage/privatestorageops/-/merge_requests/197#note_19071
-
- Jan 04, 2022
-
-
Tom Prince authored
-
- Jan 03, 2022
-
-
Tom Prince authored
-
- Dec 20, 2021
-
-
Jean-Paul Calderone authored
now all nodes load the issuer module so we can always supply issuer configuration, where it makes sense to do so, even on systems where the issuer is not going to be enabled. if that sounds silly read the comment in default.nix
-
- Sep 28, 2021
-
-
Tom Prince authored
-
- Sep 23, 2021
-
-
Tom Prince authored
-
- Sep 06, 2021
-
-
Tom Prince authored
-
Tom Prince authored
-
- Sep 03, 2021
-
-
Tom Prince authored
-
Tom Prince authored
-