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.
- $wgDisableUploads is an old variable (MW < 1.5.0). It is
$wgEnableUploads now.
- The bottom urls should point to
www.mediawiki.org
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)
You are mapping both script paths and documents inside /wiki
What would happen if I wanted to create an article named 'skins'?
How would you forbid robots accessing history urls but allow normal pages?
I'd prefer the classical /w /wiki setup.
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)
I'm a bit intrigued pn how it is finding the right LocalSettings.php,
though.
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.