I can change this to the github repos, yes, all I need to know is the "schema" of the url. Also, Reedy made the excellent suggestion of Caching results -- which I am working on -- that will also reduce both load time and heavy traffic time.
But actually, working in front of github will be somewhat easier, too, since github has a better REST API.
Are all (or most) extensions in Github under https://github.com/wikimedia/ with a "mediawiki-extensions-" prefix? Can I use that as a general rule of thumb?
On Mon, May 13, 2013 at 11:33 PM, Ryan Lane rlane32@gmail.com wrote:
On Sun, May 12, 2013 at 11:26 PM, Moriel Schottlender <moriel@gmail.com
wrote:
Hello everyone,
I'd like to get your opinions and critique on my very first MediaWiki extension, which, I hope, will be helpful to other developers.
I noticed that there's no easy way of seeing if extensions that we have installed on our MediaWiki require update, and there are even some extensions that get so little regular attention that when they do get updated, there's no real way of knowing it (unless we check
specifically).
It can be annoying when encountering problems or bugs, and then
discovering
that one of our extensions (probably the one we least expected) actually has an update that fixed this bug.
So, I thought to try and solve this issue with my extension. Since MediaWiki's changes are submitted through gerrit, I thought I'd take advantage of that and perform a remote check to see if there are any new commits that appeared in any of the extensions since they were installed.
I like the idea of this, but if this is used widely it's going to kill our gerrit server. It hits gitweb directly. Gitweb calls are uncached and are fairly expensive to run against our server. We replicate all repositories to github, and they allow this kind of thing. Is there any way you can change this to use the github replicas?
- Ryan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l