fix(uptime-kuma): !hack wait 10s before starting stateless uptime kuma #192
No reviewers
Labels
No labels
awaiting
awaiting-author
awaiting
awaiting-reviewer
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DGNum/infrastructure#192
Loading…
Reference in a new issue
No description provided.
Delete branch "sleep-uk"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -143,6 +144,8 @@ in
proxyWebsockets = true;
};
systemd.services.stateless-uptime-kuma.serviceConfig.ExecStartPre = "${lib.getExe' pkgs.coreutils "sleep"} 10";
can we have an issue in stateless-uptime-kuma tracking a proper readiness probe, ideally with systemd collaboration or something?
I am reluctant to these sorts of hacks, but I guess there's no other way.
Maintenant que le vrai fix est merge upstream, on n'a plus besoin de ça
Pull request closed