A Composer plugin to easily switch between different PHP package repositories and mirrors.
slince/composer-registry-manager is a command-line tool that helps PHP developers quickly switch between different Composer package repositories and mirrors. It simplifies managing multiple package sources, which is especially useful for developers in regions with network constraints or those needing to use private registries.
PHP developers using Composer who need to manage multiple package repositories, particularly those in regions with network limitations or using private registries.
Developers choose this tool for its simple, intuitive interface that reduces friction in switching repositories, with features like geographic filtering and custom repository management not natively available in Composer.
:hammer_and_wrench: :hammer: Composer registry manager that help to easily switch to the composer repository you want.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a clear, formatted table of all available repositories with URLs and geographic locations, as shown in the README's example output, making it easy to browse and select mirrors.
Allows filtering repositories by location (e.g., --location China), which is specifically useful for developers in regions with network constraints to find the closest mirror.
Supports adding and removing custom repositories via commands like repo:add, enabling teams to include private registries beyond the default list.
Offers an interactive command (composer repo:use) or direct name input to switch repositories globally or per-project, simplifying the process compared to manual composer.json edits.
Requires installation via `composer global require`, which can lead to conflicts with project-specific Composer versions or dependencies, and isn't ideal for isolated or containerized environments.
Focuses primarily on repository switching without native support for advanced Composer features like caching optimization, version pinning for mirrors, or integration with other Composer plugins.
As a third-party tool, it may lag in supporting new Composer versions or features, relying on maintainer updates, which could break functionality with future Composer releases.