Change Details

Until T84923 or something similar is resolved we need to have an interim way to keep RESTBase content up to date on edit, template edit, image re-upload, page move & protection. The path of least resistance is likely to hack up / fork [the existing Parsoid extension](https://github.com/wikimedia/mediawiki-extensions-Parsoid) to schedule HTTP requests to RESTBase.

Until T84923 or something similar is resolved we need to have an interim way to keep RESTBase content up to date on edit, template edit, image re-upload, page move & protection. The path of least resistance is likely to hack up / fork [the existing Parsoid extension](https://github.com/wikimedia/mediawiki-extensions-Parsoid) to schedule HTTP requests to RESTBase. This involves - doing some search & replace for the names, - some request parameter tweaking to reflect the new URL layout and update headers, and - deploying this to production just like the parsoid extension.

Until T84923 or something similar is resolved we need to have an interim way to keep RESTBase content up to date on edit, template edit, image re-upload, page move & protection. The path of least resistance is likely to hack up / fork [the existing Parsoid extension](https://github.com/wikimedia/mediawiki-extensions-Parsoid) to schedule HTTP requests to RESTBase. This involves - doing some search & replace for the names, - some request parameter tweaking to reflect the new URL layout and update headers, and - deploying this to production just like the parsoid extension.