<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Opentofu on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/opentofu/</link>
    <description>Recent content in Opentofu 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/opentofu/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Terraform Module Registries: Boring Registry vs Terrareg vs Git-Based Modules Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-18-self-hosted-terraform-module-registries-boring-registry-terrareg-git/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-18-self-hosted-terraform-module-registries-boring-registry-terrareg-git/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Terraform modules are the building blocks of Infrastructure as Code (IaC) — reusable, versioned chunks of configuration that let teams standardize their cloud infrastructure. As organizations scale their IaC practices, managing hundreds of modules across dozens of repositories becomes a challenge. Where do you store modules? How do you version them? How do teams discover which modules exist?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
