felixalb/pvv-nixos-config
1
0
Fork 0
mirror of https://git.pvv.ntnu.no/Drift/pvv-nixos-config.git synced 2026-08-11 05:42:33 +02:00
Code Issues Projects Releases Wiki Activity

treewide: add missing systemd ordering directives

Browse Source 
In particular, we were missing `sops-install-secrets.service` in a ton
of places, and `network-online.target` for some homebrewn services.

This has caused failure of some services on machine startup.
This commit is contained in:
h7x4
2026-07-22 17:56:06 +09:00
parent 9a837d210d
commit 384534bf86
27 changed files with 200 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hosts/ildkule/services/monitoring/grafana.nix
+5
View File
@@ -79,6 +79,11 @@ in {
};
};
systemd.services.grafana = {
after = [ "sops-install-secrets.service" ];
requires = [ "sops-install-secrets.service" ];
};
services.nginx.virtualHosts.${cfg.settings.server.domain} = {
enableACME = true;
forceSSL = true;
hosts/ildkule/services/monitoring/prometheus/postgres.nix
+10 -3
View File
@@ -37,9 +37,15 @@ in {
};
};
systemd.services.prometheus-postgres-exporter-knakelibrak.serviceConfig = let
localCfg = config.services.prometheus.exporters.postgres;
in lib.recursiveUpdate config.systemd.services.prometheus-postgres-exporter.serviceConfig {
systemd.services.prometheus-postgres-exporter-knakelibrak = {
after = [ "sops-install-secrets.service" ];
requires = [ "sops-install-secrets.service" ];
# TODO: is it really necessary to use recursiveUpdate on the entire attrset here?
# Why don't we just update the relevant attrs directly?
serviceConfig = let
localCfg = config.services.prometheus.exporters.postgres;
in lib.recursiveUpdate config.systemd.services.prometheus-postgres-exporter.serviceConfig {
EnvironmentFile = config.sops.secrets."keys/postgres/postgres_exporter_knakelibrak_env".path;
ExecStart = ''
${pkgs.prometheus-postgres-exporter}/bin/postgres_exporter \
@@ -48,4 +54,5 @@ in {
${lib.concatStringsSep " \\\n " localCfg.extraFlags}
'';
};
};
}