list of addons

[oasisfleeting]

https://github.com/oasisfleeting/magento-snippets/blob/master/n98-megatron.sh

[cmuench]

Nice. Thanks for providing the list. I will see if anyone in our 3rd party list. https://github.com/netz98/n98-magerun/wiki/3rd-party-magerun-projects

[tkn98]

@oasisfleeting Impressive line-up. What do you think about creating a registry file (e.g. as JSON) to keep a list of known extensions under version control? Nice name btw :)

[DavidLambauer]

+1!

[oasisfleeting]

Would love to. Thanks.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[pocallaghan]

I started work on an an extension manager plugin that could search packagist for code with a specific type e.g. "magerun-plugin". The idea was basically to piggy back the composer system to find / install plugins.

It would have commands like: plugin:add-repo Allow adding custom package list (self hosted satis installs etc.) plugin:search Use packagist API to search for a plugin plugin:list List all available plugins plugin:install Download the plugin, with options for scope like ~/, or lib/n98-magerun etc. plugin:remove Delete the plugin plugin:info Display meta information about the plugin (from composer.json)

If there's a community interest in something like this, I can try to find some time to developer it far enough to be pushed into the public domain.

[tkn98]

let me guess: Ithink there is :) :+1:

[razbakov]

this is an awesome idea, i was just thinking about the same few days ago

[robbieaverill]

I wonder if there's a way that this issue could become a kind of "implement a Magerun package manager" request, perhaps if third party modules were logged at packagist.org and tagged as a magerun-module we could run list, install, remove, update commands etc. The composer wrapper is there already which would be a good start.

[ktomk]

Very good idea with composer.

[szepeviktor]

We could have a list of commands in the module's composer.json

[ktomk]

First of all a curated list in machine readable form (e.g. a JSON file like res/modules.json) within the repo is necessary. It than can be used to generate listings or even package management.

It should also be possible to tailor your own source version of Magerun, require modules via composer and build your own phar including these additional modules. IIRC our PHAR build supports this. So composer should already work.