Hint: Speed up imports to BlueSpice

[osnard]

When importing the migration result in an existing BlueSpice installation, the process might be slow, due to the number of enabled extensions. To improve this, one can perform the import on a "modified version" of BlueSpice.

If you are using the official bluespice-deploy stack, this can be done by creating a dedicated compose/docker-compose.override.yml file like this:

services:

  wiki-importer:
    image: ${BLUESPICE_WIKI_IMAGE}
    container_name: ${COMPOSE_PROJECT_NAME:-bluespice}-wiki-importer
    environment:
      <<: *common-environment
    command: start-web
    volumes:
      - ${DATADIR}/wiki:/data
      - /tmp/LocalSettings.BlueSpice-MINI.php:/app/bluespice/w/LocalSettings.BlueSpice.php
    secrets: *common-secrets

With a /tmp/LocalSettings.BlueSpice-MINI.php like this:

<?php
wfLoadSkin( 'Vector' );
$wgDefaultSkin = 'vector';
wfLoadExtension( 'OOJSPlus' );
wfLoadExtension( 'SimpleBlogPage' );
wfLoadExtension( 'CommentStreams' );
wfLoadExtension( 'TemplateStyles');
wfLoadExtension( 'ParserFunctions');
wfLoadExtension( 'DateTimeTools');
wfLoadExtension( 'Checklists');
wfLoadExtension( 'SimpleTasks');
wfLoadExtension( 'EnhancedUploads');
wfLoadExtension( 'HeaderTabs');
wfLoadExtension( 'SubPageList');
wfLoadExtension( 'TableTools');

One can then import the migration result from the new wiki-importer container. It can be removed from the stack afterwards. The regular wiki-web and wiki-task containers should be turned off during the import.

Be aware that, as extensions like SemanticMediaWiki and BlueSpiceExtendedSearch are disabled during import, their respective datasources may need to be rebuild manually after the import. E.g. with extensions/SemanticMediaWiki/maintenance/rebuildData.php or extensions/BlueSpiceExtendedSearch/maintenance/rebuildIndex.php

[osnard]

wfLoadExtension( 'TemplateStyles');

is also required