Satis — Infrastructure¶
This section covers the server-side administration of our private Satis Composer registry. For developer usage (adding Satis to a project, installing packages), see the Satis guide.
Overview¶
The Satis instance is hosted on the Tool Server and serves our private Composer packages at packagist.subscribed.build. It runs as a Docker-based stack and is exposed securely via a Cloudflare Tunnel — no direct inbound ports are opened on the server.
| Detail | Value |
|---|---|
| Production URL | packagist.subscribed.build |
| Web interface port | 90 (internal, not exposed publicly) |
| Access restriction | Office IP via Cloudflare Access |
| Deployment | Docker Compose |
| Connectivity | Cloudflare Tunnel (connector) |
Migration history¶
On April 27, 2026 the Satis service was migrated from its legacy host to the centralised Tool Server as part of a broader effort to consolidate internal development services.
| Legacy | Current | |
|---|---|---|
| URL | packagist.barberklingen.dk | packagist.subscribed.build |
| Server path | /home/packagist/packagist | /home/packagist/packagist-test |
| Architecture | Bare install | Docker Compose |
| Connectivity | Direct | Cloudflare Tunnel |
The legacy URL remains resolvable but should not be used. All projects should point to packagist.subscribed.build.
Architecture¶
The stack runs as a set of Docker containers. Cloudflare Tunnel acts as the reverse proxy — the web interface is mapped internally to port 90 and exposed via Cloudflare's zero-trust layer. Access is restricted to office IP addresses as defined in the Cloudflare Application settings.
See Bootstrap for initial server setup and Pipeline for automated Satis index updates.