given that a straight MDM (meza deploy monolith) command can take a while.. it is understandable that there are clear situations where it doesn't make sense to re-deploy the entire meza environment just because one has changed the logo or a single config setting on a single wiki. In this specific case (a single tweak to a single wiki, say a single change in the "/opt/conf-meza/public/wikis/demo" folder - such as an edit to a file in postLocalSettings.d) .. What would be the correct way to write an MDM (meza deploy monolith) command that runs only the plays and tasks that could possibly be affected by updates to a single wiki? ty.
Topic on Talk:Meza/Commands
or.. Is it easy to say where (the server path) each live wiki is actually running out of on a meza system? I'd like to tinker with a specific wikis live localsettings.php file to get my changes right before I add them to a postLocalSetting.d php file in conf-meza/public/wikis/. If I knew where I could tinker with a wiki's live LocalSettings.php file, I would be fine with running a full MDM after I'm sure what configuration settings are wanted.
add --tags mediawiki to just do mediawiki stuff. Add --skip-tags latest,update.php to skip updating extensions and such to latest versions, and skip update.php from making sure your database is correct for latest MW and extension versions.
ok.. are you saying that there isn't a way to deploy minor changes to just one wiki?
Correct, there is no mechanism for that at the moment. You can also skip the "verify-wiki" tag if you have lots of wikis.