<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fedora on SQP Dev</title>
    <link>/tags/fedora/</link>
    <description>Recent content in Fedora on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/fedora/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Setting Up a DevOps Environment on Fedora 42</title>
      <link>/posts/2026-05-01-devops-environment-fedora-42/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-01-devops-environment-fedora-42/</guid>
      <description>&lt;p&gt;Coming from a VFX and IT background, I decided to transition into DevOps. This is the first post in a series documenting that journey.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-fedora&#34;&gt;Why Fedora?&lt;/h2&gt;&#xA;&lt;p&gt;Fedora aligns well with enterprise DevOps — the same package manager (DNF), SELinux by default, and close ties to RHEL. The quirks you solve on Fedora build exactly the troubleshooting mindset DevOps engineers need.&lt;/p&gt;&#xA;&lt;h2 id=&#34;toolbox-for-isolation&#34;&gt;Toolbox for Isolation&lt;/h2&gt;&#xA;&lt;p&gt;Rather than installing everything directly on the host, I use &lt;a href=&#34;https://containertoolbx.org/&#34;&gt;Toolbox&lt;/a&gt; — a container-based environment built on Podman. My DevOps tools live in a container called &lt;code&gt;sandbox&lt;/code&gt;, keeping the host clean.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
