After a decision with the Brickipedia community has been made, it was decided that the three wikis Customs, Ideas, and Meta should be closed down. Apparently it's possible by just removing stuff from LocalSettings related file stuff (https://github.com/Brickimedia/LocalSettings/commit/bafe7aa49535b3f8212ee46a46a812b608fac377), but the structure is pretty tangled so I don't know. @georgebarnick Do you know how to?
|Open||None||T141318 Close Customs, Ideas, and Meta wikis on the Brickimedia Farm|
|Resolved||ashley||T143377 Remove Customs, Ideas, and Meta links from DeepSea left-side header|
|Resolved||SamanthaNguyen||T143379 Remove Custom, Ideas, and Meta from Brickimedia Splash|
|Open||None||T143381 Remove Customs, Ideas, Meta and related code from LocalSettings repo at GitHub|
|Open||None||T143382 Figure out new global configuration for Brickimedia|
|Resolved||UltrasonicNXT||T143380 Create a database dump for Customs, Ideas, and Meta|
For the record: the discussion/voting page is at Brickipedia:2016 Changes. I had somehow missed the fact that we decided to close Meta, which is gonna require a lot more effort than the other two sites, because Meta hosts things like the email blacklist, MediaWiki:Global.css and whatnot, not to mention almost 100k files.
Closing Customs and Ideas should be simpler:
- Create a database dump (via mysqldump)
- Remove relevant entries from LocalSettings.php (the switch loop, $bmAllProjects/$wgLocalDatabases variable, $wgConf->settings, the $refreshed<project to be closed> variable,
- Remove relevant entry from $newTalkGlobalDatabases, $wgSiteMatrixSites and $wgLocalDatabases in LocalSettings_ext.php
- Edit other LocalSettings (e.g. LocalSettings_gbc.php and such which are not going to be deleted) to update the $wgRefreshedHeader['dropdown'] variable to remove the removed sites from the drop-down menu (won't be needed if T134669 is (partially) fixed)
- Delete the LocalSettings file for the site(s) to be deleted, e.g. LocalSettings_ideas.php
- Commit these changes to the LocalSettings repository (Brickimedia/LocalSettings on GitHub)
- Deploy new configuration to production
While creating a database dump is -- at least in theory -- easy enough, we need to figure out where to store the created dump and for how long. (It contains some sensitive data, I'm sure, so it shouldn't be a public location.)
I also don't know how to properly deploy a new version of the config repo, and there are probably some uncommitted live changes on production anyway that we'd need to commit before going further with this.