Future plans

[ozh]

Use this in YOURLS core along with wikimedia/composer-merge-plugin

YOURLS' composer.json would be added this:

    "extra": {
        "merge-plugin": {
            "include": ["user/composer.json"]
        }
    },

Adding a plugin would be done either with:

• editing user/composer.json, or composer require -d user ozh/example-plugin --no-update
• then running composer update --lock

Then the idea would be to have a shortcut for this with a custom command
Something like:

    "scripts": {
        "add-plugin": "bash ./includes/somewhere/add-plugin"
    }

With add-plugin being a script like

# do some checks on  $@ and make sure we have a 'vendor/package' argument
# display some help, etc ...

# check if composer is in path
if ! command -v composer > /dev/null ; then
    echo "composer not in path, do this:"
    echo "composer require -d user $1 --no-update"
    echo "composer update --lock"
    exit 1
fi

# all right, go
composer require -d user $1 --no-update
composer update --lock

[ozh]

Or, probably better than a bash script, a custom PHP command -- https://getcomposer.org/doc/articles/plugins.md#command-provider

[ozh]

composer add-plugin custom command done :) That was interesting :)

[ozh]

Hmmm, not there yet, the custom command isn't a sane idea after all.

What I need to achieve is that the user simply composer require my/plugin and the installer takes care of everything, no need to specify -d or to update stuff.

[ozh]

So. The custom command is a sane idea after all.

• composer require my/package : add to root composer.json
• composer add-plugin my/package : add to user/composer.json
• composer remove-plugin my/package
  These 2 commands work with a YOURLS plugin or any package, and will install in the appropriate location (/user/plugins or /includes/vendor)

Now to write unit tests