From c508d7a30de7f735cdcecb885b7e5e0251e59f55 Mon Sep 17 00:00:00 2001
From: Gabriel Arazas <foodogsquared@foodogsquared.one>
Date: Tue, 7 Feb 2023 09:47:01 +0800
Subject: [PATCH] hosts/plover: update dump limit script

---
 hosts/plover/modules/services/gitea.nix | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/hosts/plover/modules/services/gitea.nix b/hosts/plover/modules/services/gitea.nix
index 9708143b..82891b15 100644
--- a/hosts/plover/modules/services/gitea.nix
+++ b/hosts/plover/modules/services/gitea.nix
@@ -106,11 +106,10 @@ in
 
   # Disk space is always assumed to be limited so we're really only limited
   # with 2 dumps.
-  systemd.services.gitea-dump.serviceConfig = {
-    ExecStartPre = pkgs.writeShellScript "gitea-dump-limit" ''
-      ${pkgs.findutils}/bin/find ${config.services.gitea.dump.backupDir} -mtime 14 -maxdepth 1 -type f -delete
-    '';
-  };
+  systemd.services.gitea-dump.preStart = lib.mkAfter ''
+    ${pkgs.findutils}/bin/find ${lib.escapeShellArg config.services.gitea.dump.backupDir} \
+      -mtime 14 -maxdepth 1 -type f -delete
+  '';
 
   # Making sure this plays nicely with the database service of choice. Take
   # note, we're mainly using secure schema usage pattern here as described from