<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Semaphore on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/semaphore/</link>
    <description>Recent content in Semaphore on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/semaphore/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Ansible Automation Platforms: AWX vs Semaphore vs Rundeck</title>
      <link>https://www.pistack.xyz/posts/2026-06-18-ansible-automation-platforms-awx-semaphore-rundeck/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-18-ansible-automation-platforms-awx-semaphore-rundeck/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Ansible has become the lingua franca of IT automation — but running playbooks from a developer&amp;rsquo;s laptop does not scale. As teams grow, you need a centralized platform that provides role-based access control, job scheduling, audit logging, and a web UI for less technical team members. This is where self-hosted Ansible automation platforms come in: they wrap Ansible&amp;rsquo;s CLI power in a collaborative web interface suitable for production operations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
