<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pypi on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pypi/</link>
    <description>Recent content in Pypi on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 03 May 2026 17:05:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pypi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Dependency Proxy: Verdaccio, DevPI, and Nexus Repository Cache Comparison</title>
      <link>https://www.pistack.xyz/posts/2026-05-03-self-hosted-dependency-proxy-verdaccio-devpi-nexus-cache-guide/</link>
      <pubDate>Sun, 03 May 2026 17:05:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-03-self-hosted-dependency-proxy-verdaccio-devpi-nexus-cache-guide/</guid>
      <description>&lt;p&gt;A self-hosted dependency proxy caches packages from external registries (npm, PyPI, Docker Hub, Maven Central) on your local network. This reduces download times, protects against upstream outages, and lets you control which package versions enter your development and production environments. While full package registries host private packages, a &lt;strong&gt;dependency proxy&lt;/strong&gt; specifically focuses on caching external registries for faster, more reliable dependency resolution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
