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:
On 16/10/12 13:32, Johannes Weberhofer wrote:
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.
Johannes
Very interesting.
Note that in README.DISTRIBUTION:
- MediaWiki works with some more dbs than mysql and postgresql.
- Apache requeriment is not a strict one, pretty much any web server
with php support would work.
That's true, I've added some more text to the file
- $wgDisableUploads is an old variable (MW <
1.5.0). It is
$wgEnableUploads now.
Thank you for recognize that. I've corrected the text.
- The bottom urls should point to
www.mediawiki.org
Didn't check that for a while. Modified it.
The makealias.sh looks quite pretty but
Alias /wiki/common
$TARGETDIR/webroot/common
We don't have a common folder (we do have
skins/common but that's
included in skins alias)
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
You are mapping both script paths and documents inside
/wiki
What would happen if I wanted to create an article named 'skins'?
All Pages start with an uppercase-letter, so there should be no problem
related to that.
How would you forbid robots accessing history urls but
allow normal pages?
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'd prefer the classical /w /wiki setup.
I don't prefer none of the setups; for some reason I decided to use
this setup some years ago.
It's a bit obscure how $MW_SYSDIRS, $MW_LINKFILES,
are created in
admintools/files in the spec file. (you're also symlinking more files
than needed, but it's better to symlink too much than too few)
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.
I'm a bit intrigued pn how it is finding the right
LocalSettings.php,
though.
Pleas explain me more...
PS: Is is possible to clone the repository of the
package specs?
Although there's clearly a repository backend, I was unable to find it.
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