I recall at one point setting up a set of wiki, where I symlinked the
common folders (extensions, includes, languages, maintenance, etc...) to
a common area.
As I recall, maintenance scripts didn't work right. From what it looked
like, the scripts were trying to find a settings folder relative to the
common folder.
So I have a feeling that any case of symlinking or wild carding would
suffer from the same issue.
And there's always the possibility of adding a cli accepted parameter
which the settings file accepts as the ID. Then you just pass that
parameter and the settings intercepts that and makes the maintenance
scripts work.
I've actually got a bit of development on a wiki hosting company through
a bit.
The setup I have is quite interesting.
/mw#_## - is actually where MediaWiki is located.
/GlobalSettings.php - holds the global settings (Actually it only does a
few base stuff then includes the split files)
/configs/globals/*.php - Holds the actual finer Global Settings (I split
settings into multiple files grouped together into something like
"2-Permissions.php" because settings can get fairly large and disorganized)
/configs/locals/*.php - Holds the local settings for a wiki. (However,
these are likely going to be special variables which are not used in
MediaWiki, but used in the globals to define things further; Using a
configuration script to generate these)
/configs/versions/* - Holds files with codes like "mw1_11". ((Though,
now that I'm using /configs/locals for a different type of variables, I
may merge these into there; But that's debatable))
But the primary attraction is this file:
/index.php
It's actually a special little script. It strips down the domain till it
has a identifier for the wiki (Or if it's an external domain it will
later search /configs/aliases/domains/ for a file telling what wiki to
alias to). And uses that to find the /configs/versions/* to determine
what mw#_## to use. Actually, urls in the form
"wikiname.mw1_11.hostname.com" also work to.
The general idea is that even though every domain is directed to the one
set of files, the wiki can potentially run different versions of
MediaWiki. And, there is no wait for DNS changes when adding a new wiki
under subdomain.
But my primary purpose for this is actually for updating. I thought of
this method, so that it would be possible for me to update one wiki at
at time when I need to do schema updates to the database. Without being
forced to db lock a potential 1000+ wiki, to update them all.
~Daniel Friesen(Dantman) of:
-The Gaiapedia (
http://gaia.wikia.com)
-Wikia ACG on
Wikia.com (
http://wikia.com/wiki/Wikia_ACG)
-and
Wiki-Tools.com (
http://wiki-tools.com)
jidanni(a)jidanni.org wrote:
D> the ultimate solution would be to wildcard all
your domains to one
D> set of files
Then you couldn't do
$ cd aaaa/maintenance; php somescript.php #e.g., to upgrade
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l