@Anomie Thanks for your quick reply! The MediaWiki Stakeholder group is actually working on an appropriate replacement for Extension:LdapAuthentication. It's likely to be a combination of Extension:PluggableAuth and Extension:PuggableSSO (plus some other extensions :) )
Is there any documentation on when and how to use "LdapPrimaryAuthenticationProvider"? On the official extension page I did not find any information about it.
@Raymond Sorry for the mess I've created with the first six extensions. I've merged them all now. Can you take care of the "mediawiki-extensions.txt"? I promise next time I'll be more careful.
As extension.jsonallows to invoke the composer autoloader ("load_composer_autoloader": true) you can already make use of composers classmap feature.
Tue, Sep 19
Mon, Sep 18
Thu, Sep 14
Wed, Sep 13
I don't mean that this should be implemented in Extension:Configure, but the other way round. Having a detailed description of particular configuration options (like a description, data type, possible values, ...) is the first step to build a user interface that provides proper input fields (e.g. a "Namespace-Selector") to modify them. At the moment Extension:Configure does exact that. Unfortunately it is broken with MW 1.29 and I believe, that if someone is going to change that, the new/next version of Extension:Configure should probably use the available information from the extension registry. Ideally an extension should be allowed to provide a custom input type. A mapping between input type and configuration would be needed though
Tue, Sep 12
Is this something Extension:Configure should be build upon? The extension page tells that it is not compatible with MW1.29. Does anybody know whether the author already works on this?
@Legoktm thanks for clarification. Will "load_composer_autoloader" : true in extension.json then be dropped?
Mon, Sep 11
Thu, Sep 7
Wed, Sep 6
Mon, Sep 4
Fri, Sep 1
Thu, Aug 31
From a third party user and extension developer perspective I'd be totally okay with PHP7 as requirement.
Regarding the question of how extensions should use namespaces:
Aug 11 2017
@Tgr Is a namespace convention like MediaWiki\Extensions\<extension name> or MediaWiki\Skins\<skin name> somewhere documented? Or better are there any examples of extensions that already do use such namespaces? Background of my question is, that the BlueSpice-team is going to use namespaces (and composer based PSR-4 autoloading) for future development. And we are still discussing about conventions. I want our new code to be as close to MediaWiki conventions as possible.
Aug 9 2017
- Good use of the MediaWiki framework (e.g. using framework provided functions instead of native PHP or external library functions)
Aug 2 2017
Jul 31 2017
Jul 28 2017
Jul 21 2017
Jul 19 2017
Jul 18 2017
Awesome, thank you. Really the double quotes?
Jul 17 2017
@Paladox I test only with MediaWikiCore@REL1_27.
Jul 13 2017
Jul 12 2017
Five day ago https://gerrit.wikimedia.org/r/#/c/325081/ got merged and thus introducing a merge conflict to my backport. Fortunately by this it got possible to cherry-pick the original change to REL1_27, which I did. I also cherry-picked to REL1_28 as this is the current stable. I abandoned my backport.
Jul 7 2017
Jun 30 2017
Jun 1 2017
May 31 2017
May 29 2017
May 26 2017
Are there any chances that change "If648d6e218847e6632d643ea724cd3da3945db70" gets backported to REL1_27 LTS?
May 24 2017
Never mind. I'll just keep watching what you are doing in your respository :) You plan to have parsiod/mathiod and stuff as a separate container? Will the images be published to hub.docker.com and how are chances that those images can be considered "official"?
May 22 2017
- Created stub of https://www.mediawiki.org/wiki/LDAP_hub
- Created stub of https://www.mediawiki.org/wiki/LDAP_hub/Migration_from_extension_LDAPAuthentication
- Created stub of https://www.mediawiki.org/wiki/LDAP_hub/Migration_from_extension_LDAPAuthentication/Example_1
- Created stub of https://www.mediawiki.org/wiki/LDAP_hub/Extension:LDAPAuthentication/Hint
May 20 2017
To sum the docker topic up: There are currently three approaches:
- By @Addshore: Uses docker-compose, consists of services "mediawiki-mysql", "mediawiki-mariadb", "mediawiki-phpmyadmin", "mediawiki-nginx-php5", "mediawiki-nginx-php7", "mediawiki-nginx-hhvm", "mediawiki-apache-php5", "mediawiki-apache-php7", "mediawiki-apache-hhvm", "mediawiki-graphite-statsd" and "mediawiki-nginx-proxy". See https://github.com/addshore/mediawiki-docker-dev - Seems to be quite a lot of stuff with some redundancy, but probably covers a lot of cases
- By @GWicke: Uses docker-compose, consists of services "db" and "web". See https://github.com/wikimedia/mediawiki-docker - The "web" service has a pretty sophisticated DOCKERFILE and entrypoint.sh. It seems to me as almost all WMF infratructure is missing, even Parsoid.
- By WikiToLearn: Didn't find docker-compose here, but there are a lot of docker image builds available. See https://hub.docker.com/u/wikitolearn/ - Some of the highlights seem to be OCG, RestBase, Mathiod and Parsoid. It looks like those are crafted for production purposes and not for development (e.g. Parsoid is being configured to run with multiple language specific subdomains).
So here are the minutes of our session: https://etherpad.wikimedia.org/p/fixing-ldap
May 19 2017
Thanks for the hint, Bernhard!
May 17 2017
Yes, me :) I've also set up my own docker-based dev environment and would love to learn what other people are doing.