<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conda on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/conda/</link>
    <description>Recent content in Conda on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/conda/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Conda Package Servers: Quetz vs conda-store vs conda-mirror</title>
      <link>https://www.pistack.xyz/posts/2026-06-10-self-hosted-conda-package-servers-quetz-conda-store-conda-mirror/</link>
      <pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-10-self-hosted-conda-package-servers-quetz-conda-store-conda-mirror/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Scientific computing teams, data science platforms, and enterprise machine learning groups face a critical dependency management challenge: how to provide reproducible, auditable, and internally curated Python and R package repositories. Public channels like conda-forge and Anaconda&amp;rsquo;s defaults channel solve discovery, but they introduce external dependency risk, rate limiting, and lack of control over package provenance in regulated or air-gapped environments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
