Help talk:Single Node MediaWiki
E3 approach
Here's how E3 configured the editor engagement instances kubo and piramido. Suggestions and feedback welcome. -- spage (talk) 05:29, 13 October 2012 (UTC)
puppet checks out git master to /srv/mediawiki.
But thereafter it leaves it alone, so 2012's fiddling to move /srv/mediawiki elsewhere isn't necessary. Just follow Help:Git#Shared repositories on labs to make the git repo writable.
To track the current wikimedia branch:
- get the MediaWiki version, then
- Now check out a tracking branch for that particular MediaWiki branch, e.g. 1.22wmf16
- git branch --track wmf/1.22wmf16 origin/wmf/1.22wmf16
- git checkout wmf/1.22wmf16
- To get all the extension versions associated with this release
- git submodule update --init --recursive
To set up a configuration closer to production: All the relevant settings are on http://noc.wikimedia.org/ and in the gerrit project operations/mediawiki-config.git in wmf-config directory, but..
- It seems challenging to use the InitialSettings.php and CommonSettings.php from production, they use Conf.php to build local globals from arrays of database instances.
- these files do have a simpler set up for a "testwiki" configuration (the $wgDBName of your labs instance), but they then assume this applies to the web server named test.wikipedia.org
- Maybe use the beta labs wmfconfig?
Perhaps the best you can do is copy lots of settings and require_once( "$IP/extensions/ExtName/ExtName.php" );
lines into orig/LocalSettings.php. Don't forget to run php maintenance/update.php
Overriding QuestyCaptcha
The puppet config for a MediaWiki labs instance requires ConfirmEdit/QuestyCaptcha.php in LocalSettings.php. If you want to switch to the FancyCaptcha word images as used on WMF wikis:
- replace this file with a zero-length file
- in orig/LocalSettings.php require ConfirmEdit/ConfirmEdit.php and ConfirmEdit/FancyCaptcha.php
- One way to get the images is
- run the script ConfirmEdit/createcaptcha.py on another machine to create the images
- copy them to a directory on your labs instance such as /mnt/fancycaptcha.
- Set $wgCaptchaDirectory to this directory and $wgCaptchaSecret to the secret you used.
Other approaches
- Deployment/Overview describes the detailed complex setup to configure beta labs more like production
- Nova Resource:Integration/Setup has various notes on setting up a MediaWiki instance and supporting packages; this is much more manual with less use of puppet
Alternatives
- An alternative to running a labs instance is running MediaWiki in a VM on your own hardware. https://github.com/atdt/wmf-vagrant is a packaged VM that uses puppet to self-update some of its features.
Extensions?
How I can install extensions on it (in the clean way using puppet configuration or...)? I probably want just install VisualEditor and Parsoid but a general guide for a simple extension would be really nice and suffice. ebrahim (talk) 15:01, 16 December 2013 (UTC)
- You can install extensions using Mediawiki_singlenode::Mw-extension[<extensionname>]. If you look at /modules/wikidata_singlenode/manifests there's an example of a spiffed up mediawiki install. I'm not sure about Parsoid and VE, though, they may require more work than just adding extensions. andrew (talk) 14:22, 20 December 2013 (UTC)