Add a wiki

From Wikitech-static
Revision as of 19:27, 22 July 2015 by imported>Alex Monk (→‎MediaWiki configuration: rm echowikis.dblist)
Jump to navigation Jump to search

This page will walk you through how to add a new wiki project. This includes new languages on sister projects, and wikis for committees, chapters etc.


  • Tell in advance the Ops list, springle, jcrespo (jynus) or Coren that this is happening so the storage layer can be prepared and checked (labs, backups, dumps). In particular, the following things should be clear:
    • Is the wiki public (available to read for all people)? If so, the wiki will need to be replicated to labs.
    • Should the wiki be added to the general backup and disaster recovery system of production wikis?

Usually, the answer is "yes to both" or "yes to the last one".

This can be fixed after the wiki creation, but it is more painful/involves custom queries.


  • First of all, the DNS entry for the new wiki has to be added. Make the following changes to your local checkout of operations/dns.git and submit to gerrit for review.
    • If it is a language project, add the language code to /templates/helpers/langs.tmpl in operations/dns repo. If it is not a new language, then it has probably been done already as these are shared by all the sister projects.
    • If it is a wiki in * domain (chapter wiki or special wiki), add it to /templates/ Make sure to add a mobile entry if necessary.
  • Merge the change in gerrit and run authdns-update. Query the DNS servers to make sure it has been correctly deployed. See DNS#HOWTO for details.

Apache configuration

You will firstly have to login to our deployment host. As of sometime, this is the host tin, you will have to go via bast1001. Then gather all relevant information for the new project, including all configuration variables and entries. Each wiki will have different requirements (project name, namespaces, extensions to be enabled etc).

You now have to determine if this is a new language project (say something like Spanish Wikibooks) or a chapter wiki, or a special wiki (anything else, including private wikis). Then choose the correct part of this manual:

Language Project


IMPORTANT: For Private Wikis

  • Private wiki databases must not be replicated to the labsdb MySQL instances!
    • Before creating a database for a new private wiki, make sure to add the db name to the puppet global array $private_wikis in manifests\realm.pp.
    • Deploy this config change with puppet and manually restart the Prelabsdb-db (Sanitarium) MySQL instance that will house this wiki's db (most likely s3).
    • If you need help with this, please ask a member of the Ops team for help. This is very important.

MediaWiki configuration

Database list Purpose
Database lists of wikis in each MySQL database cluster
all.dblist All wikis should be listed in here
closed.dblist Any closed (no write access, full read access) wikis
deleted.dblist Any deleted wikis
Database lists of wikis arranged into their relevant size
flaggedrevs.dblist All wikis running the FlaggedRevs extension
securepollglobal.dblist $wgSecurePollCreateWikiGroups wikis: Board Election wikis
visualeditor-default.dblist All wikis where VisualEditor is enabled by default
commonsuploads.dblist All wikis which should have local uploading soft-disabled. Uploads go to Commons instead.
fishbowl.dblist All fishbowl (restricted write access, full read access) wikis
private.dblist All private (read and write restricted) wikis
special.dblist All special wikis
wikidata.dblist All wikis running the Wikidata repo
wikidataclient.dblist All wikis running the Wikidata client
wikimania.dblist All Wikimania wikis
wikimedia.dblist All chapter wikis
wikibooks.dblist All Wikibooks wikis
wikinews.dblist All Wikinews wikis
wikipedia.dblist All Wikipedia wikis
wikiquote.dblist All Wikiquote wikis
wikisource.dblist All Wikisource wikis
wikiversity.dblist All Wikiversity wikis
wikivoyage.dblist All Wikivoyage wikis
wiktionary.dblist All Wiktionary wikis
  • Now it is time to actually create the database (this script also performs other tasks, such as notifying the 'newprojects' mailing list). There are two different ways to do this, depending on if you did Part A, B, or C above:
  • mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki languagecode projectname databasename domain
  • Part A is for standard language additions to projects, like adding a Spanish Wikinews, which will be my example.
  • mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki languagecode projectname databasename domain
  • EG: mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki es wikinews eswikinews to add a Spanish Wikinews.
  • Part B is for Chapters Wikis. My example will be adding a Finnish chapter wiki:
  • mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki languagecode projectname databasename domain
  • EG: mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki fi wikimedia fiwikimedia
  • Part C is for non-standard special wikis such as committees, chapters, and the like. My example will be
  • mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki languagecode projectname databasename domain
  • EG: mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki en wikimedia strategywiki

(Note the 'aawiki' in these examples: aawiki is in s3, so this will create the database in s3, which is usually the right place for new small wikis.)

  • Merge the config change in Gerrit, and pull it onto tin
  • Check *.dblist files now contain the new wiki
  • Run sync-dblist to synchronize all database lists
  • Check wikiversions.json is sane
  • Run sync-wikiversions to synchronize the version number to use for this wiki
  • Run sync-file wmf-config/InitialiseSettings.php
  • Run sync-file w/static/images/project-logos/path-to-logo.png
  • Run sync-file langlist (this must be done before the interwiki cache below)
  • Unless it's a language project, update the meta:Interwiki map
  • updateinterwikicache


You shouldn't have to do much (maybe adjust shard sizes preemptively if it'll be big), the index should be automatically created by addWiki.php and all wikis now opt into Cirrus/Elastic by default. See Search/New#Adding_new_wikis for more information.


  • Public wikis:
    • Create the container for thumbnails. mwscript extensions/WikimediaMaintenance/filebackend/setZoneAccess.php databasename --backend=local-multiwrite
  • Private wikis:
    • Create the container for thumbnails. mwscript extensions/WikimediaMaintenance/filebackend/setZoneAccess.php databasename --backend=local-multiwrite --private



  • Add to wikidataclient.dblist and sync-dblist (might need to touch/sync InitialiseSettings/CommonSettings)

sites table

  • Add the new wiki to all site tables of current wikidataclient wikis and also wikidatawiki.
  • Populate the sites table on the new wiki, which can be done with the populateSitesTable script in Wikibase. It has to be run once for each site group (e.g. wikipedia, wikivoyage, ...), as well as for wikidata (wikidata.dblist, with --site-group wikipedia) and commons (--site-group wikipedia).

Both of these steps can be done with populateSitesTable:

foreachwikiindblist wikidataclient.dblist extensions/Wikidata/extensions/Wikibase/lib/maintenance/populateSitesTable.php --force-protocol https

In addition to updating the sites table, the script clears the sites cache (memcached) which is needed for things to work correctly.

sorting of language interwiki sidebar list

  • Potentially some actions required in Wikibase repository for new languages to be sorted properly: phabricator:T103044

After you finished

If there's something to import (as is often the case in new Language wikis), someone will do so, following the process described at MetaWikipedia:incubator:Incubator:Importing from Incubator (logged at MetaWikipedia:incubator:Incubator:Site creation log).

See also Delete a wiki.