mirror of
https://github.com/zadam/trilium.git
synced 2026-09-14 11:06:04 +05:00
a05d1e9518
The Dockerfiles set only --start-period, so the interval and timeout came from Docker's defaults. The 30s interval spends 2880 cold node processes a day on machines that are otherwise idle, and the 30s timeout was dead config: probeHealth() caps itself at 2s, so Docker's own timer could never fire. Vaultwarden, Outline and Uptime Kuma all settled on 60s; the projects still at 30s got there by inheriting the default rather than choosing it. --start-period goes to 30s so a first boot that creates the schema, runs a migration or checks consistency is not reported unhealthy, and so the CI step that waits 50s for a healthy container keeps its slack now that a missed probe retries a minute later instead of 30s later. A successful probe ends the window immediately, so a normal boot pays none of it. Worst case time to unhealthy moves from ~100s to ~210s. Nothing acts on that signal on its own, so the cost is a human reading docker ps later. assertHealthcheckStaysSmall() justifies its bundle ceiling with the probe's cadence, so its comment moves to 60 seconds too. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build-server.sh | ||
| build.ts | ||
| export-schema.sh | ||
| generate_document.ts | ||
| generate-cert.sh | ||