You can control most of the paths MediaWiki uses using some config settings.

For upload use these: http://www.mediawiki.org/wiki/Manual:$wgUploadDirectory http://www.mediawiki.org/wiki/Manual:$wgUploadPath

There's no way to store images inside the database unless you build your own FileRepo impl, even then it would be a mess when things like thumbnailing are done.

Multiple sites sharing the same code is done by using some domain or path tests inside the LocalSettings.php file (that's half the reason it's a php file and not a flat config file).

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

On 11-07-03 10:13 AM, Igor Chudov wrote:

I happen to have several wikis.

Some of them are nonworking, but I have database dumps.

I am trying to recreate them, and I want to do a nice job.

Specifically, I want to

a) Share the same code base b) Keep them in separate MySQL databases c) Preferably, keep images in databases to ease backup.

What really irks me at the moment, is that a mediawiki installation has local data (LocalSettings, images etc) completely intermixed with code.

Is there some way to separate this? To have code in one place and several directories with data in another place?

I did read a few instructions and was slightly put off by needing to create a cornucopia of symbolic links, etc.

I wonder if, perhaps, there is some mediawiki implementation that separates data from code in some nice, clean way.

Thanks a lot, guys!

Igor