We want to see if we can generate the json configuration without a pre-existing mediawiki installation and check if there is a way we can split up the json configuration so we can mount it as a config map for a containerized mediawiki.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T263166 Convert static mediawiki configuration to form more suitable for containers | |||
| Open | None | T267057 Experiment with generating json config | |||
| Declined | None | T267058 Understand how people use mediawiki-config |
Event Timeline
Comment Actions
See T223602: Define variant Wikimedia production config in compiled, static files for the previous work in this area where myself and James have analyzed most all of this already with the container use case in mind.
I don't think any of it requires a MW installation, but it is certainly written with that assumption in mind since that's how MW works today. E.g. when referring to a namespace ID, there's no reason not to use the namespace constants like NS_MAIN or NS_USER. Those would be easy to substitute or define locally, however.
The CI job for wmf-config already runs standalone without a MW install.