<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Boudaakkar Nazih</title>
    <description>The latest articles on DEV Community by Boudaakkar Nazih (@spounka).</description>
    <link>https://dev.to/spounka</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F411749%2F3ed912e8-df35-42fa-bb82-33651f1441bb.jpg</url>
      <title>DEV Community: Boudaakkar Nazih</title>
      <link>https://dev.to/spounka</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/spounka"/>
    <language>en</language>
    <item>
      <title>The versatile ntfy</title>
      <dc:creator>Boudaakkar Nazih</dc:creator>
      <pubDate>Sat, 19 Sep 2026 10:52:05 +0000</pubDate>
      <link>https://dev.to/spounka/the-versatile-ntfy-4i3e</link>
      <guid>https://dev.to/spounka/the-versatile-ntfy-4i3e</guid>
      <description>&lt;p&gt;Greetings everyone.&lt;/p&gt;

&lt;p&gt;Ever run a long backup job only find out it failed a day later? Yeah, and I hate it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.nazih.top/posts/the-versatile-ntfy/" rel="noopener noreferrer"&gt;In my latest blog post&lt;/a&gt;, I walk through setting up ntfy via Docker Compose to catch failures in custom scripts (PostgreSQL backups in my case) and automatically push alert notifications, with failure logs attached, directly to your devices using simple curl commands.&lt;/p&gt;

&lt;p&gt;Have a great one&lt;/p&gt;

&lt;p&gt;PS: feedback is still very welcome, this blogging thing is a work in progress&lt;/p&gt;

</description>
      <category>automation</category>
      <category>devops</category>
      <category>docker</category>
    </item>
    <item>
      <title>Why I prefer systemd Timers</title>
      <dc:creator>Boudaakkar Nazih</dc:creator>
      <pubDate>Fri, 18 Sep 2026 20:08:56 +0000</pubDate>
      <link>https://dev.to/spounka/why-i-prefer-systemd-timers-2obo</link>
      <guid>https://dev.to/spounka/why-i-prefer-systemd-timers-2obo</guid>
      <description>&lt;p&gt;Most users would schedule their tasks using a cronjob, and that's perfectly reasonable.&lt;/p&gt;

&lt;p&gt;Cronjobs are essentially used for scheduling tasks at certain intervals or exact time(s).&lt;/p&gt;

&lt;p&gt;But what happens when the machine goes down at &lt;code&gt;00:00&lt;/code&gt;? or something even more probable, cron's systemd unit (like cronie) stops or does not start because someone forgot to (re)enable it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Answer: The job &lt;em&gt;never&lt;/em&gt; runs&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.nazih.top/posts/systemd-timers/" rel="noopener noreferrer"&gt;In this linked blog post&lt;/a&gt;, I explain why I prefer using systemd timers in such business critical situations&lt;/p&gt;

&lt;p&gt;Have a great one.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>backup</category>
      <category>scheduling</category>
    </item>
  </channel>
</rss>
