Some extensions (like "Widgets") require Apache to have "write" permission in a specific sub-folder within the extension.
So installing the Widgets extension requires the server admin to run something like
sudo chmod 775 /opt/htdocs/mediawiki/extensions/Widgets/compiled_template
Unfortunately, MEZA deploy resets all of the permissions in the extensions folder to be read-only for apache - requiring an admin to manually go back in after a deploy and re-set the folder permissions in specific folders for the extensions to run right.
It would be of great benefit if an admin could specify these commands somewhere in the meza configuration and meza deploy would automatically run them after every successful deploy.
Environment
Issue details
Some extensions (like "Widgets") require Apache to have "write" permission in a specific sub-folder within the extension.
So installing the Widgets extension requires the server admin to run something like
sudo chmod 775 /opt/htdocs/mediawiki/extensions/Widgets/compiled_templateUnfortunately, MEZA deploy resets all of the permissions in the extensions folder to be read-only for apache - requiring an admin to manually go back in after a deploy and re-set the folder permissions in specific folders for the extensions to run right.
It would be of great benefit if an admin could specify these commands somewhere in the meza configuration and meza deploy would automatically run them after every successful deploy.
Thank you.