modules/taskchampion-sync: Avoid issue with DynamicUser

1 files changed, 14 insertions, 1 deletions

diff --git a/modules/by-name/ta/taskchampion-sync/module.nix b/modules/by-name/ta/taskchampion-sync/module.nix
index a722883..a7cba30 100644
--- a/modules/by-name/ta/taskchampion-sync/module.nix
+++ b/modules/by-name/ta/taskchampion-sync/module.nix
@@ -18,7 +18,10 @@ in {
 
   config = lib.mkIf cfg.enable {
     users = {
-      users.taskchampion.uid = config.vhack.constants.ids.uids.taskchampion;
+      users.taskchampion = {
+        uid = config.vhack.constants.ids.uids.taskchampion;
+        group = "taskchampion";
+      };
       groups.taskchampion.gid = config.vhack.constants.ids.uids.taskchampion;
     };
 
@@ -34,6 +37,16 @@ in {
       nginx.enable = true;
     };
 
+    systemd.services.taskchampion-sync-server = {
+      serviceConfig = {
+        # The upstream service uses DynamicUsers, which currently poses issues to our
+        # directory persisting strategy.
+        User = "taskchampion";
+        Group = "taskchampion";
+        DynamicUser = lib.mkForce false;
+      };
+    };
+
     services = {
       taskchampion-sync-server = {
         enable = true;