Change Details

My rough idea is there would be a Vagrant role that is somehow configurable: - one can define multiple wikis to be created - Wikibase extension would be enabled on each of those wikis - one would define whether Client, Repo, or both components should be enabled on each wiki (ie. there could be different component set up on each wiki, not the same on all) - one could define which of other Wikibase-related extensions (e.g. MediaInfo, Lexeme, but why not also Quality External Validation etc) should be enabled on each wiki (again, different config for each wiki). - possibly the role would also configure interwikis/sites of each wikis so they are aware of each other. - configuring repos to be federated and/or clients to use particular repo (or repos) with the same config mechanism would be nice but I am expecting this to be rather complex, so leaving this to be configured (manually) in each wiki's LocalSettings seems fair. I started to think about when preparing test system on Labs for the "federated repositories" feature of Wikibase extension. Existing "wikidata" and "wikibase_repo" roles do not really provide the desired flexibility (from some perspective they either configure too much, or too little)

My rough idea is there would be a Vagrant role that is somehow configurable: - one can define multiple wikis to be created - Wikibase extension would be enabled on each of those wikis - one would define whether Client, Repo, or both components should be enabled on each wiki (ie. there could be different component set up on each wiki, not the same on all) - one could define which of other Wikibase-related extensions (e.g. MediaInfo, Lexeme, but why not also Quality External Validation etc) should be enabled on each wiki (again, different config for each wiki). - possibly the role would also configure interwikis/sites of each wikis so they are aware of each other. - configuring repos to be federated and/or clients to use particular repo (or repos) with the same config mechanism would be nice but I am expecting this to be rather complex, so leaving this to be configured (manually) in each wiki's LocalSettings seems fair. I started to think about when preparing test system on Labs for the "federated repositories" feature of Wikibase extension (T156114). Existing "wikidata" and "wikibase_repo" roles do not really provide the desired flexibility (from some perspective they either configure too much, or too little)

My rough idea is there would be a Vagrant role that is somehow configurable: - one can define multiple wikis to be created - Wikibase extension would be enabled on each of those wikis - one would define whether Client, Repo, or both components should be enabled on each wiki (ie. there could be different component set up on each wiki, not the same on all) - one could define which of other Wikibase-related extensions (e.g. MediaInfo, Lexeme, but why not also Quality External Validation etc) should be enabled on each wiki (again, different config for each wiki). - possibly the role would also configure interwikis/sites of each wikis so they are aware of each other. - configuring repos to be federated and/or clients to use particular repo (or repos) with the same config mechanism would be nice but I am expecting this to be rather complex, so leaving this to be configured (manually) in each wiki's LocalSettings seems fair. I started to think about when preparing test system on Labs for the "federated repositories" feature of Wikibase extension (T156114). Existing "wikidata" and "wikibase_repo" roles do not really provide the desired flexibility (from some perspective they either configure too much, or too little)