Mirroring a wiki

[lahwaacz]

References:

• https://github.com/WikiTeam/wikiteam/
• https://www.mediawiki.org/wiki/Manual:Grabbers
• https://www.mediawiki.org/wiki/API:Database_field_and_API_property_associations
• https://www.mediawiki.org/wiki/Incremental_dumps
• https://dumps.wikimedia.org/other/incr/

To do list:

• abstraction for working with an SQL database
  • only a couple of tables of interest, similar but not exactly the same schema as MediaWiki has (compatibility only via the API layer - see below)
  • for inspiration:
    • https://github.com/rkabir/mwdb
    • http://pythonhosted.org/mediawiki-utilities/core/database.html
    • https://github.com/mediawiki-utilities/python-mwdb
• grabbers for fetching important tables from API
  • namespace, namespace_name (custom tables)
  • recentchanges, logging
  • user, user_groups, ipblocks
  • page, page_props, page_restrictions, protected_titles
  • archive, revision, text: wait for list=allrevisions module in MediaWiki 1.27 https://phabricator.wikimedia.org/T113885
  • tags
  • interwiki
• handle difficult actions involving DELETE or UPDATE queries as part of the syncing process:
  • removing from user groups
  • unblock
  • unprotect
  • delete (move from revision to archive)
  • undelete (move from archive to revision, also check page_id)
  • selective undelete
  • merge (works assuming that both source and target page were not deleted before the sync)
  • import (works assuming that the imported pages were not deleted/merged/whatever before the sync)
  • delete/revision, delete/event
  • tag/update (separately for recentchanges, logging, revision, archive)
  • other log events: https://wiki.archlinux.org/api.php?action=help&modules=query%2Blogevents
• let the SQL database serve as a source of data instead of the API
  • list=recentchanges
  • list=logevents
  • list=allpages
  • list=protectedtitles
  • list=allrevisions
  • list=alldeletedrevisions
  • titles=, pageids= for use with prop=
  • common executor for the DB select queries (for easy profiling)
• framework for tests
  • pytest fixture for web server (nginx)
  • pytest fixture for php-fpm
  • pytest fixture for MediaWiki installation (depends on nginx, php-fpm, postgresql + MW sources, config, initial SQL)
  • write the tests...
  • implement a double-source wrapper, which yields from the API and checks the DB selects, ignoring NotImplementedErrors etc. (usable for unit tests as well as real-world testing) split into Double-source wrapper for API and DB queries #50

[lahwaacz]

Upstream bug reports which block further improvement:

• archiving:
  • list=alldeletedrevisions returns pageid=0 instead of ar_page_id
  • Make ar_parent_id visible through the API
  • Use ar_parent_id on undeletion
• merging:
  • MergeHistory: record the target page ID in the log events (merged into log_params doesn't contain the page ID of the target page in merge events)
  • MergeHistory: timestamp-based midpoints are not sufficient

[lahwaacz]

This is somewhat finished and working nicely, so it's time to close this.