Project Canasta/Infrastructure solution

This is an informal RFC/RFP for finding/creating a system to generate downloadables for the project known as Project Canasta. Project Canasta, in brief, is aimed at enabling easy-installed MediaWiki instances that contain not just MediaWiki but also skins and extension, and a set of wiki pages, that together can fulfill some use case. Part of that task involves finding, or creating, a solution to generate these downloadables.

The solution should meet as many as possible of the following criteria:

(The person generating the downloadable is referred to here as a "creator", and the person downloading it is referred as an "administrator".)


 * The solution should let the creator specify a set of skins and extensions, and configurations for each (separately or just through one LocalSettings.php file). It should then generate a downloadable file or image. That file, when downloaded, should allow an administrator to simply run some command, and then, with a minimum of options presented, the script should generate an entire MediaWiki instance, as well as a database that is set up and initialized for both MediaWiki and all the installed extensions. This should include having a database user and password that are generated - perhaps in real time by the script - and then stored in LocalSettings.php.


 * Ideally the creator can specify whether or not this downloadable should additionally include instances of PHP, a DB system and a web server (e.g., MySQL and Apache), and potentially an operating system as well (e.g., CentOS). That way, administrators will have their choice of whether they want a container that includes all of these, or whether they want to use their own existing systems and simply download/install MediaWiki.


 * Additionally, the solution should be fully open source, and it should be relatively easy for a creator to run on their system.

Please create sections below for any existing solutions that could be used for this purpose, briefly explaining how they work and whether they could be made to fit all of these criteria.

Linux/Docker: dataspectsSystemBuilder approach
''The principles and concepts of the following use case steps are implemented and I use them almost every week. For now and in the context of Canasta, they shall represent my current opinion of an optimal integration/abstraction level.''

Creator
The CreatorProcess (e.g. Meza, BlueSpice, dataspectsSystemBuilder, ...) shall deliver the following CreatorArtefacts components:


 * a MediaWiki root folder $MEDIAWIKI_ROOT_FOLDER containing a certain MediaWiki Canasta version (see below)
 * a corresponding database $DATABASE_NAME at $MYSQL_HOST used by $MYSQL_USER identified by $MYSQL_USER_PASSWORD
 * a docker-compose.yml file (e.g. https://github.com/dataspects/dataspectsSystemBuilder/blob/master/docker-compose.yml)

This represents a certain version, e.g. mediawiki-canasta-1.35.0-201215-* (see below), consisting of:


 * a specific MediaWiki core version
 * a specific set of versioned MediaWiki extensions and skins
 * a specific LocalSettings.php configuration

MediaWiki Canasta versioning ideas

 * mediawiki-canasta-1.35.0-201215-single-standard
 * mediawiki-canasta-1.35.0-201215-single-crm
 * mediawiki-canasta-1.35.0-201215-single-documentManagement

Packer
The PackerProcess shall deliver the following PackerArtefacts in the $MEDIAWIKI_CANASTA_DISTRIBUTION_FOLDER:

produced by the following bash file build-distribution-package.sh:
 * a $MEDIAWIKI_DISTRIBUTION_ARCHIVE
 * a $MEDIAWIKI_DATABASE_DUMP in the $MEDIAWIKI_DISTRIBUTION_ARCHIVE

Installer
The InstallerProcess runs in the $SYSTEM_ROOT_FOLDER using the following InstallerArtecfacts as $SYSTEM_ROOT_FOLDER_OWNER:

install-distribution-package.sh
https://github.com/dataspects/dataspectsSystemBuilder/blob/master/install-distribution-package.sh

Upgrader
The UpgraderProcess requires an upgraded $MEDIAWIKI_CANASTA_ARCHIVE in the $SYSTEM_ROOT_FOLDER.

The upgrade is then executed by the following bash file switch-canasta-version.sh: