On 15/10/12 19:57, Axel Thimm wrote: What patch are you using? How is it configured? You need some config switching somewhere. Perhaps the LocalSettings.php from MediaWiki POV could simply select from different subordinate LocalSettings.php May I ask why would you want this? Ideally, you shouldn't ever need anything other than the latest version. The custom config at the user LocalSettings.php would need to reflect somewhere in your setup. You mean as used for locating the files and as basis for the $wg*Directory variables? Seems doable easily. Any suggestion for the name of the "data $IP" ?

Hi, On Mon, Oct 15, 2012 at 09:48:32PM +0200, Platonides wrote: http://pkgs.fedoraproject.org/cgit/mediawiki.git/tree/mediawiki-1.16.2-comm… It uses $IP as the code path and $DIR as the data path. The patch worked by splitting the paths based on the current working directory (= instance path) vs a hard coded path for the mediawiki code). In a pakaged distribution an upgrade of mediawiki w/o keeping the previous version would imply automatically running the mathing upgrade.php scripts on each instance. First of all, I'd prefer if this is done by the user/admin of the instance. And next it may be that on a hosting wiki farm different users will want to upgrade at different times. But that is more a packaging issue that can be easily solved with the current upstream code. The user's LocalSettings.php doesn't need to be patched if the main code is to split the $IP variable (as done in the patch). The only thing left is how to setup the code path. The patch mentioned above uses a dirty hardwired path. A cleaner solution would allow to specify a different code path from the current working directory (but default to the current working directory to keep backwards compatible). I used $DIR which is as bad as a name could had been, so I'll admit to zero creativity in name giving. :/ Something that reflects "instance", "data", (local) "config" etc. -- Axel.Thimm at ATrpms.net

For opensuse I've developed scripts which allows simple installation and updates of several mediawiki instances. You could have a look at the scripts in https://build.opensuse.org/stage/package/files?package=mediawiki&projec… There is makealias.sh, which builds up a symlinked structure and suggests an apache configuration (based on mediawiki's short urls. The suggested config also tries to seperate the individual installations completly by setting some php-parameters. All created wikis are listed in /etc/mediawiki-installations to be used by update.sh which incorporates the single updates and some service-works, depending on the version upgrades. There are no patches needed to operate the wiki (there is only one patch for an upload problem included, which should be removed when I'm updateing to release 1.20). Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna

Platonides, thank you very much for your review! I'll incorporate some changes in the next release. Am 16.10.2012 18:30, schrieb Platonides: That's true, I've added some more text to the file Thank you for recognize that. I've corrected the text. Didn't check that for a while. Modified it. Hmm... Don't know why I have added that. I'm quite sure, there was some reason; I've removed it, as it's definitely no longer needed All Pages start with an uppercase-letter, so there should be no problem related to that. I'd never thought about that; I've seen that there is '<meta name="robots" content="noindex,nofollow" />' included in HTML, so robots shouldn't index older versions. I don't prefer none of the setups; for some reason I decided to use this setup some years ago. That's created in the spec files; I had some problems with the updates around MW 1.17 when there were some major changes regarding the load.php and api.php; those things could be simplified I think. Pleas explain me more... It's a opensuse build service repository. To download it, you must install the osc client from the repository in http://download.opensuse.org/repositories/openSUSE:/Tools/ (it supports lot of OS); There is a manual at http://en.opensuse.org/openSUSE:OSC Once you have installed the client, you can execute "osc co server:php:applications mediawiki". Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna

Am 17.10.2012 11:43, schrieb Platonides: I'm changing to that with the next release. Do you mean the maintenance scripts on the command line or the hosted sites? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna