• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Getting Composer to recognise auxiliary json files

Dengro

New Pleskian
Support for Composer is a rather welcome addition to Plesk (many thanks for this!), especially if you're reliant on shared hosting. Unfortunately, I'm having trouble making good use of it on MediaWiki installations.

The problem is that while MediaWiki comes with its own composer.json file, it defers any additional extensions and libraries to a file called composer.local.json. From the docs:

"MediaWiki core "owns" $IP/composer.json and will change the contents of that file in both tarball and Git managed updates. In order to allow local installs to use Composer to load optional libraries and/or manage extensions with Composer, a special plugin for Composer named composer-merge-plugin was developed. This plugin and the MediaWiki core composer.json configuration allow a local deployment to add required extensions and libraries to a file composer.local.json inside the root MediaWiki directory."

Is there any way we can tell Plesk to look for composer.local.json files as well? If not, could such a feature be added to a future release?

Some useful links:
Composer - MediaWiki
Help:Installation/Example "composer.local.json" file - semantic-mediawiki.org
 
I know this post reporting this issue is quite old but I would like to know if someone knows about it or if the Plesk team is working on it.

Thanks in advance, and thank you @Dengro for reporting it.
 
Back
Top