<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Salt-Stack on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/salt-stack/</link>
    <description>Recent content in Salt-Stack on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/salt-stack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Uyuni vs Foreman vs Salt Stack: Self-Hosted Patch Management Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-02-uyuni-vs-foreman-vs-salt-stack-self-hosted-patch-management-guide-2026/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-02-uyuni-vs-foreman-vs-salt-stack-self-hosted-patch-management-guide-2026/</guid>
      <description>&lt;p&gt;Keeping servers patched and up to date is one of the most fundamental — and most neglected — operational tasks in any infrastructure. Unpatched systems are the single largest attack vector for ransomware, data breaches, and compliance failures. Commercial patch management platforms from vendors like Tivoli, ManageEngine, and Automox charge per-node licensing fees that quickly become unsustainable at scale, while also requiring your vulnerability data to flow through cloud infrastructure.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
