I have technically added nginx support for the icinga2 module when i was testing on test1.

I've moved phabricator and lizard.miraheze.org to nginx.

piwik.miraheze.org has been renamed to matomo.miraheze.org and is now behind varnish.

This is interesting.. might as well keep an eye on it (especially because it includes Phabricator, Analytics, and Icinga)

It is over the past month (as of yesterday). I’ll need to look at the total number of visits.

That's awesome! Thank you so much. It certainly needs polishing, but I love that your made that... much quicker than expected!

Doesn’t look ugly to me. Works great. Nicely done.

Right, Special:Analytics on every wiki now works.

Hi! I'm so happy you are making progress with this task! I checked the link and I miss individual page views, like a top-ten or something similar. Also, the most-searched words using the wiki search field would be interesting in order to see which are the most user-wanted articles.

This is now done and running. Should take changes to take affect 10-20mins.

And with this, the backend is done.

The next major step is done (sort of!), with this commit I added a wrapper function that can easily be used to query the API and then with this commit I made use of it initially to produce an array of the number of visits to a wiki per device. Below I've included a sample output on the command line for metawiki to show the sort of data I intend to implement to a special page eventually.

Okay, quick status update for people.

done.

Fantastic stuff. Will definitely get used and tested by the wiki I maintain.

Right, this is super early stuff now but https://github.com/miraheze/MatomoAnalytics is live and is where all the development work will be going. I'm aiming to make this an officially supported extension which will work with any MediaWiki and Matomo installation in either a farm or single wiki only set up. This will potentially slow down overall progress as I try and make the extension work for all from the start but given how long this has been a task for us and how complex the situation looks, I'm sure people won't mind.

First steps taken towards this with the introduction of a hook into CreateWiki allowing additional steps to be added to the process of creating a wiki by different extensions.

@Paladox On test1, I've made two separate pages for Extensions and Settings (https://test1.miraheze.org/wiki/Special:ManageWikiSettings) and (https://test1.miraheze.org/wiki/Special:ManageWikiExtensions).

ManageWiki needs to be an easily usable tool + we need to implement as many settings as we can on it so therefore I think this task is important and should be made a goal

We have switched to swift now.

Various attempted solutions etc. seen around ...

• https://www.mediawiki.org/wiki/Extension:ExternalLinks
• https://www.mediawiki.org/wiki/DeadlinkChecker
• https://meta.wikimedia.org/wiki/Fixing_dead_links
• https://meta.wikimedia.org/wiki/InternetArchiveBot
• https://www.mediawiki.org/wiki/Manual:Pywikibot/refLinks
• https://www.mediawiki.org/wiki/Manual:Pywikibot/weblinkchecker.py
• https://en.wikipedia.org/wiki/Link_rot
• https://en.wikipedia.org/wiki/Wikipedia:Link_rot
• https://en.wikipedia.org/wiki/User:InternetArchiveBot

A nice thing to provide all wikis with, easily an achievable development goal. Therefore adding this as a goal for July-December this year thought I expect to get to it (if no one else does!) by the end of August at the latest.

Ok, we have switched to swift now, we are finding it unstable when someone uploads a image, it causes mw* to slow down so much it is depooled by varnish.

swift1 sounds better!

or just plain simply swift1?

im thinking sw1 or im1?

@Southparkfan needs another 512MB CVZ in NL (with name to be determined). Approval on T3101#61045

High and "target for the next 6 months" is very conflicting.

Using Goal-2018-Jul-Dec so that we doin't rush our selfs to get this done by the end of this month.