Unverified Commit 432d274c authored by Maximilian Bosch's avatar Maximilian Bosch
Browse files

nixos/nextcloud-notify_push: use RestartMode=direct 

`nextcloud-notify_push.service` requires
`nextcloud-notify_push-setup.service`. If the latter fails (e.g. because
of Nextcloud not being there yet), the push service would also fail with
result 'dependency'.

RestartMode=direct doesn't put a unit into failed state IF it's about to
be restarted again. That way, `nextcloud-notify_push` will await several
restart attempts. Only if the unit fails due to a rate-limit (i.e. too
many restarts), the push service will also fail.

If the startup is still too slow, it may make sense for administrators to
configure higher intervals between the start attempts with RestartSec.
parent 8583a0de

nixos/modules/services/web-apps/nextcloud-notify_push.nix

+2 −0
Original line number Diff line number Diff line
@@ -144,6 +144,8 @@ in 
          Group = "nextcloud";

          ExecStart = "${lib.getExe cfgN.occ} notify_push:setup ${cfg.nextcloudUrl}/push";

          LoadCredential = config.systemd.services.nextcloud-cron.serviceConfig.LoadCredential;

          RestartMode = "direct";

          Restart = "on-failure";

        };

      };

    };