https://bugzilla.wikimedia.org/show_bug.cgi?id=65188
Tyler Romeo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Tyler Romeo <[email protected]> --- (In reply to Ori Livneh from comment #3) > A skeleton extensions.json would be checked into git but then added to > gitignore so that subsequent modifications don't dirty the repo state. We'd have to call it extensions-example.json, because once a file is added to the repository, gitignore will no longer affect it. (In reply to Ori Livneh from comment #3) > We'd implement a mediawiki-instance installer (like > <https://github.com/composer/installers/blob/master/src/Composer/Installers/ > MediaWikiInstaller.php> is a mediawiki-plugin installer). > > The installer would merge additional requirements from an extensions.json > file, if present. I think this is a pretty viable solution. My only concern is that now people would have to manually edit extensions.json in order to install new extensions. Which is why maybe we should take the Vagrant approach! It seems the Composer\Plugin\PluginInterface is meant to install plugins into Composer. Do we know if it would be possible to add custom commands to composer, similar to how we add "list-roles" with Vagrant? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
