(We can also use YAML object extends if the PHP configuration is transformed in YAML)

Did some tests with the artwork uploaded to Zed hypership tower. We've a crop+resize problem to solve there: artwork is generally in landscape format, and the thumbnails to generate are 162x162.

Plan is to temporarily increase $wgMaxImageArea from 12500000 to 15000000, so we can generate thumbnail for our files.

What I like with this idea is we can move the actual YAML configuration to pillar/saas/mediawiki/wikis.sls, provision it through roles/saas-mediawiki/saas and make saas-mediawiki repository read the YAML file.

Could have been a permission issue because the /var/dataroot/www.wolfplex.org/images folder has been created by 7dfd539c.

WithLog::getLoggerConfiguration() provides the logger configuration.

Probably best to install Mathoid service - https://www.mediawiki.org/wiki/Manual:Mathoid

Tested here: https://www.wolfplex.org/wiki/Fichier:Nasqueron_logo.png

Fixed by the MediaWiki SaaS, the wiki runs under mediawikiand we've /var/dataroot/<wiki name>/images belonging to the mediawiki user for that.

A core group is still OK from a database point of view, but totally missing from SaaS configuration.

When done, D2270 can be simplified into:

Apparently fixed in D1562, where a template variable %%serverName%% is used instead.

Assigning back to @inidal for config change against rSAASMW.

Database created

I reviewed the default Echo configuration, it is acceptable.