<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cron - Tag - vo.rs</title><link>https://vo.rs/tags/cron/</link><description>Cron - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 21 Nov 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/cron/" rel="self" type="application/rss+xml"/><item><title>Healthchecks.io (Self-Hosted): Making Sure Your Cron Jobs Actually Ran</title><link>https://vo.rs/story/healthchecksio-self-hosted-making-sure-your-cron-jobs-actually-ran/</link><description>&lt;p&gt;Here is a story that has happened to almost everyone who has ever written a cron job. You set up a nightly backup. You test it once, it works, you feel responsible and adult. Eight months later you actually need that backup, and you discover it stopped running in March because of a full disk, an expired token, or a typo you made while &amp;ldquo;tidying up.&amp;rdquo; The cron job didn&amp;rsquo;t fail loudly. It failed &lt;em&gt;silently&lt;/em&gt;, which is the worst way for anything to fail, and nobody told you because there was nobody to tell.&lt;/p&gt;</description><pubDate>Tue, 21 Nov 2023 09:00:00 +0000</pubDate></item></channel></rss>