Mirror External Registries Into Your Pricore Organization

Maarten Bode
Maarten Bode

Pricore v0.48.0 introduces Registry Mirrors, a new way to import packages from external Composer registries into your Pricore organization. Whether you’re running an internal Satis repository, subscribing to commercial PHP packages, or using paid WordPress plugins that offer Composer access, you can now centralize everything in one place.

The problem

Most PHP teams end up with multiple Composer repositories in their composer.json. An internal Satis server here, a paid plugin registry there, maybe another vendor’s private feed. Each one comes with its own credentials, its own configuration, and its own potential point of failure.

Every developer on your team needs access tokens or credentials for each of these registries. That means managing secrets across machines, onboarding new team members with a growing list of auth.json entries, and hoping nothing expires mid-deploy.

How Registry Mirrors solve this

Registry Mirrors connect to an external Composer registry, fetch all available packages and their version metadata, and import them into your organization. Your team installs everything from a single Composer endpoint with a single access token. No more juggling multiple repositories or distributing credentials.

Adding a mirror takes less than a minute. Navigate to Organization Settings > Registry Mirrors, enter the registry URL, choose an authentication method (HTTP Basic, Bearer Token, or none), and Pricore starts syncing immediately.

Mirrors sync automatically every 4 hours, and you can trigger a manual sync at any time. Only new or changed versions are processed, so syncs stay fast.

Dist mirroring

When you enable dist mirroring, Pricore downloads and stores the zip archives from the upstream registry locally. This means your team members don’t need any credentials to the original registry. They install everything through Pricore, and Pricore handles the upstream authentication.

This is especially useful for commercial packages and paid plugins where you’d otherwise need to share license keys or access tokens with every developer on your team.

Get started

feature composer registry
Back to blog