<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Package-Registry on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/package-registry/</link>
    <description>Recent content in Package-Registry on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/package-registry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Geminabox vs Gemstash vs Gem in a Box: Self-Hosted Ruby Gem Server Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-05-self-hosted-ruby-gem-servers-geminabox-gemstash-gem-in-a-box-guide/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-05-self-hosted-ruby-gem-servers-geminabox-gemstash-gem-in-a-box-guide/</guid>
      <description>&lt;p&gt;When managing Ruby projects across teams, relying on rubygems.org for every dependency download is slow, risky, and bandwidth-intensive. Self-hosted gem servers cache upstream gems, host private gems, and ensure your CI/CD pipelines never break when rubygems.org has an outage.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
