Create an event / plugin for Composer

Question

I have developed a Webserver Portable and am also creating a Portable console to use Composer.

I have a problem. I need to create a plugin for Composer.

I need that when downloading any package with Composer, it edits the "scripts" of the composer.json of that package, so that it works on the Portable console.

When downloading Laravel, for example:

Original Composer.json:

{
    "name": "laravel/laravel",
    ...
    "scripts": {
        "post-root-package-install": [
            "php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        ...
    },
    ...
}

Composer.json edited by the plugin:

{
    "name": "laravel/laravel",
    ...
    "scripts": {
        "post-root-package-install": [
            "F:/portable_php_path/php.exe -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        ...
    },
    ...
}

• Note that a physical path was generated for php.exe, because in the Portable version, it could be in any path.

(My question is about creating the Composer plugin. I have no problem editing the.json composer with PHP)

I read the tutorial to create a plugin on the Composer site, but I got confused. (https://getcomposer.org/doc/articles/plugins.md)

If you have another way to do this, it’s also interesting. I accept other suggestions and ideas.

I thank anyone who can help.

Answer 1

When running Composer via command line PHP is probably already in variable PATH of the operating system, then it is not necessary to pass the full PHP path:

"F:/portable_php_path/php.exe -r \"file_exists('.env') || copy('.env.example', '.env');\""

Just call it that:

 "php -r \"file_exists('.env') || copy('.env.example', '.env');\""

This is because Composer is written in PHP and depends on it, so the CLI interface will always be available when using Composer

To create PACKAGES for Composer see this reply:

• How to create my own package for Buy on github?

Of course you can use other types of repositories, such as Bitbucket and even repositories of your own, but if something like this specifies that it will be easier to explain in the answer.

PSR-0, PSR-4 and autoload

I recommend that before learning how to create a package to Composer learn about PSR-4 and PSR-0 (this is in disuse, but there are still packages that use it):

• PSR-0: http://www.php-fig.org/psr/psr-0/
• PSR-4: http://www.php-fig.org/psr/psr-4/
• What is spl_autoloader_register in PHP?
• PSR-4 in an MVC project or not?
• What are the differences between __autoload and spl_autoload_register?
• What does PSR mean?
• Autoload PSR4 class