I recently released a set of Ansible playbooks that will build a wiki
family on a minimal CentOS or RedHat 6.7 or 7 platform. There are also
playbooks included to create a new wiki on a wiki family and to clone a
wiki from one wiki family to another. I'm happy to accept patches to add
support to other platforms. You can clone the playbooks from
https://gerrit.wikimedia.org/r/mediawiki/tools/ansible-wikifarm. From the
README file (you can read the entire file at
This repository contains ansible playbooks for installing and configuring
MediaWiki wiki farms. A wiki farm can comprise multiple web front end
hosts, referred to as wiki families, each hosting multiple wikis. These
playbooks support either installing MediaWiki and its database on a single
host or splitting them between two tiers.
These playbooks will install MySQL, Apache, Squid, MediaWiki, and MediaWiki
skins/extensions in a single directory hierarchy (possibly separated between
two hosts as described above) and configure SELinux. This directory hierarchy
is self-contained, supporting migration between similarly configured hosts.
The wikis hosted by the wiki farms built by these playbooks will be accessed
over HTTPS with a permanenent redirect to HTTPS if accessed over HTTP. These
playbooks have been tested using ansible 18.104.22.168 to provision CentOS/RedHat 6
and 7 targets.
Date: Wed, 18 May 2016 19:53:43 -0500
> From: Daren Welsh <darenwelsh(a)gmail.com>
> To: MediaWiki announcements and site admin list
> Subject: Re: [MediaWiki-l] wiki family advice
> Content-Type: text/plain; charset=UTF-8
> A friend and I have been developing a scripted "platform" that takes a
> barebones CentOS 7 installation and with a couple commands will set up a
> wiki farm (or family) and import data from existing wikis. We're planning
> to announce its release for others to use "soon". If you're interested in
> trying it out, the first step would be to get your wikis all updated to a
> somewhat recent version. We have experience in starting with 1.23 wikis and
> upgrading them to 1.25 with this script.
> On Wed, May 18, 2016 at 3:31 PM, Bill Traynor <btraynor(a)gmail.com> wrote:
> > Hello,
> > I've got 9 old wikis running various versions of MW from 1.16 to 1.20.
> > All have their own database on a single database server. I've been
> > asked to move all of the wikis onto one app server sharing one
> > installation of MediaWiki. I understand that this is a wiki family
> > configuration.
> > Should I upgrade all of the wikis first, then move them?
> > Has anyone done this before using version 1.26 or greater and nginx as
> > the webserver?
> > Advice on the approach to take here would be appreciated.
> > I've tried to follow the instructions on the wiki family page, but
> > none seem to meet my requirements.
> > Thanks
> > Bill
> > _______________________________________________
> > MediaWiki-l mailing list
> > To unsubscribe, go to:
> > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
I've got 9 old wikis running various versions of MW from 1.16 to 1.20.
All have their own database on a single database server. I've been
asked to move all of the wikis onto one app server sharing one
installation of MediaWiki. I understand that this is a wiki family
Should I upgrade all of the wikis first, then move them?
Has anyone done this before using version 1.26 or greater and nginx as
Advice on the approach to take here would be appreciated.
I've tried to follow the instructions on the wiki family page, but
none seem to meet my requirements.
Any chance someone can point me to why pywikibot works with a 1.24 mw
instance, but not with the 1.22 one?
I can login but I can't push pages using pagefromfile.
Any clues maybe?
I’m not sure if this is the right place to ask this. I’m using foreground skin on my MW 1.26 but unfortunately the tabs are not showing up. Otherwise headertabs is running.
Firebug doesn’t find some errors. So what do you think is the reason for this?
Florian Geißler, M.Sc.
Florian Geißler, M.Sc.
EMWCon, the (first-ever) Enterprise MediaWiki Conference, is happening in
just two weeks, on May 25-27 in New York City. There will be at least 30
people attending, from a variety of different organizations and about five
different countries. The event will feature a lot of interesting talks as
well as a "Create Camp" on Friday, a sort of hackathon for both technical
and non-technical projects (and semi-technical ones).
It's not too late to register - if you're interested, go here:
probably after an automatic upgrade of mediawiki software, the content of the
pages on linueve.org/old is no more visible. However the source code is still
What can I do ?
thanks for help
SolveMedia is an ad-based captcha. I have an ancient 1.19 with it that
works, but I can't get it to work with 1.26 on PHP 5.5.9. PHP in
strict/warnings mode throws up:
Notice: Undefined index: adcopy_challenge in
on line 129
Notice: Undefined index: adcopy_response in
on line 130
- but those are problems in the working version too.
The official SolveMedia extension was last updated in 2012 and that's
the version running on this 1.19.
Has anyone got this to work on any more recent MediaWikis?
(yes it's a terrible idea in several ways, but let's assume for the
moment it's considered a tolerable baseline.)
I am Abhinand N and I have been selected for GSoC'16 for the project -
Extension for page creation/editing notification. I would like to share my
experience in contributing to MediaWiki and my perspective on implementing
the extension in MediaWiki.
I am a first year Computer Science major from Amrita University, India. I
am coming from a small town called Palakkad
<https://en.wikipedia.org/wiki/Palakkad_district> in Kerala
<https://en.wikipedia.org/wiki/Kerala>. Kerala is known as Gods own Country
and it is a very beautiful place. I got introduced to MediaWiki through
FOSS community in my campus - FOSS@Amrita <http://foss.amrita.ac.in/>. Its
one of the active club in the campus where we are introduced to a new world
of open source technology apart from the usual academic work. I started
contributing to MediaWiki by fixing small bugs. I noticed this project when
it was put up as featured for GSoC. I went through the project description
the project and got very much excited to work on the same. Yaron Koren is
my mentor for this project. He is one of the coolest guy whom I have ever
met and I am very happy to work with him.
This project aims to create notification when a page is created or edited
by any user. There are already existing modules like Watchlist, Semantic
Watchlist, PageCreationNotif etc that helps with notification. However, the
extension that I am going to develop allows the user to configure the
notification system the way he/she needs. The configuration is not limited
to whether the user needs to receive the notification via Email, Echo
notification or as the recent changes in a special page. Also, the user is
given the option to track all pages, pages in specific namespace or
category, or a specified list of pages.
Just as the pages to be tracked are grouped, the people who are to be
notified are also grouped as
- User in a user group,
- A user in a user-list,
- User who signed up to be notified or
- to Email addresses of non MediaWiki users.
That's a brief explanation about the project. Currently I haven't yet
decided on how the extension should be structured and on the user interface
part of the extension, which is one of the most important things to be
considered. Also the priority of the events are not concluded. I would be
grateful to get your valuable suggestions and feedback about the project.
It would help me a lot to make the extension more effective and convenient
for the user.
About <http://www.abhinand7.me/> | Blog
<https://abhilovesto.wordpress.com/> | Github