<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Composer on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/composer/</link>
    <description>Recent content in Composer on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/composer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PHP Composer Repositories: Satis vs Packeton vs Satisfy Compared (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-self-hosted-php-composer-repositories-satis-packeton-satisfy/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-self-hosted-php-composer-repositories-satis-packeton-satisfy/</guid>
      <description>&lt;p&gt;The PHP ecosystem relies on &lt;a href=&#34;https://packagist.org&#34;&gt;Packagist&lt;/a&gt; as its central package repository, but organizations handling proprietary code need private Composer repositories for internal distribution. Whether you are shipping internal libraries across teams, managing licensed dependencies, or working in environments with restricted internet access, a self-hosted Composer repository gives you control over package availability, access, and versioning.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
