How to refactor the Composer source management tool CRM into a composer plug-in

CRM is a command line tool I made a long time ago to managecomposersources. It is designed to use simple commands to manage multiple sources. China mirror switching, so as to manage them conveniently;

At that time, I didn’t know much about the composer plug-in, so the method was relatively rough. The bottom layer was to execute the composer command to achieve the purpose of switching sources, and it was used on Linux Fortunately, there is almost no special perception, but the win will be a bit sluggish. This is also obvious, after all, when switching, it is equivalent to executing multiple commands at the same time; later, due to the opportunity of work, I learned about the development of the composer plug-in, so the idea of refactoring came up;

with 1.x Compared with the version, 2.x mainly has the following changes:

Metadata storage location changes

In the 1.x version, it is under the user's Home folder A customized file, all user operations are ultimately persisted to this json file; the new version stores metadata in config.json under the composer global path:

{ "config": { "_alias": { "val": "validate", "up": "update", "req-sf": "require symfony/event-dispatcher symfony/console", "req": "require", "i": "install" }, "_repositories": [{ "name": "composer", "url": "https://packagist.org", "homepage": "", "author": "" }, { "name": "phpcomposer", "url": "https://packagist.phpcomposer.com", "homepage": "", "author": "" }, { "name": "composer-proxy", "url": "https://packagist.composer-proxy.org", "homepage": "", "author": "" }, { "name": "laravel-china", "url": "https://packagist.laravel-china.org", "homepage": "", "author": "" }] }, "repositories": { "packagist": { "type": "composer", "url": "https://packagist.laravel-china.org" } } }

This is maintained by composer We borrowed a file and occupied a field in it. This is also more in line with the composer ecosystem

Command changes

1.x version is an independent entry application, and the commands all start with the crm keyword, such as crm ls; in the new version In the plug-in, crm becomes a command provider role, so in the new version we use the composer entry;

New version usage

List all available images

$ composer repo:ls composer https://packagist.org phpcomposer https://packagist.phpcomposer.com * composer-proxy https://packagist.composer-proxy.org laravel-china https://packagist.laravel-china.org

The mark "*" indicates the source currently in use;

Switch mirror

$ composer repo:use Please select your favorite registry (defaults to composer) [0] composer [1] phpcomposer [2] composer-proxy [3] laravel-china >

You can also directly append the mirror name to skip selecting

$ composer repo:use phpcomposer

Add option- -current/-c switches the source for the current project. The default is to modify the global source.

All commands

Execute the following command to view

$ composer repo

Summary

In addition to the changes in usage, the most significant improvement in the new version may be the speed improvement; such as If you have any questions, you are welcome to give feedback. You can leave a message under the post or post to github issues.

I hope this small tool will bring convenience to everyone in their work and development.

For more programming related content, please pay attention to theProgramming Introductioncolumn on the php Chinese website!

The above is the detailed content of How to refactor the Composer source management tool CRM into a composer plug-in. For more information, please follow other related articles on the PHP Chinese website!