<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Go on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/go/</link>
    <description>Recent content in Go on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Athens vs GOPROXY: Self-Hosted Go Module Proxy Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-30-athens-vs-goproxy-self-hosted-go-module-proxy-guide-2026/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-30-athens-vs-goproxy-self-hosted-go-module-proxy-guide-2026/</guid>
      <description>&lt;p&gt;Every Go project depends on external modules — from the standard library extensions to third-party packages pulled from proxy.golang.org. Relying entirely on public module proxies introduces real risks that compound as your team and codebase grow. Build pipelines break when upstream proxies go down, supply chain attacks slip through unchecked module downloads, and network egress costs spiral with every CI run pulling the same dependencies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
