purgeList.php looks very outdated and purgeChangedFiles only picks up lists from specific tables.
|mediawiki/core : master||Maintenance script to purge specific page|
|Resolved||Gilles||T121388 Service-based thumbnailing re-architecture in production with Thumbor|
|Open||None||T43371 Thumbnail/imagescaler (tracking)|
|Resolved||Gilles||T168949 Proper thumbnails of portrait photos not being generated; serious display issues|
|Resolved||Gilles||T169072 Due to missing fonts on Thumbor hosts, PNG thumbnail of SVG file showing a Devanagari character only displays a Unicode number box|
|Resolved||Gilles||T169195 Write maintenance script to purge specific files and their old versions|
purgeList.php looks very outdated
Have you considered improving it instead of adding just another purge maintenance script? It's hard to tell the difference between both, and the lack of documentation doesn't help. It's confusing to have 2 scripts to purge pages.
I brought this up in code review. In the end, I believe the difference is justified, however naming and documentation could definitely be improved.
- purgeList.php: This is specifically for purging external proxies only (e.g. Varnish, Squid). It is primarily URL-based, but also supports a title or namespace, in which case it will make urls for all those pages and purge those.
- This is a relatively soft purge and has no impact on the MediaWiki application.
- This script can also be used for urls that do not relate to a wiki page. For example, one single thumbnail url, a /w/load.php url, a /w/api.php url, a static file from a skin or interface such as /w/resources/assets/poweredby_mediawiki_88x31.png or /w/skins/Vector/images/user-icon.png.
- purgePage.php: This is the equivalent to action=purge and does a lot. For example:
- It re-parses the wikitext, it saves changes to the database (e.g. current expansion of magic words and templates, writes links to the database for images, links-here, categories etc.).
- It also performs a database write for page.page_touched to the current time, which has potential cascading effects to other areas of the application.
- It also purges the page's canonical urls from File cache (wgUseFileCache) and/or from external Squid/Varnish proxy. (This is the part that purgeList.php does)
- In addition, individual page types (such as FilePage) and extensions, may register additional actions. For example, when purging a File page, we also delete thumbnails from Swift storage, and purge the urls of all thumbnail sizes and variations (page1, page2, 120px, 320px etc. etc.)