Hi, Tom Hughes wrote: > We have one little Atom based machine. They have a metric buttload of > database servers serving pages to ten metric buttloads of web servers > fronted by about a thousand metric buttloads of squid caches.
Then don't be such a sissy and get use the metric buttload of servers we need for the wiki! Who needs to access nodes and ways when they can instead access wiki pages ;-) > It doesn't help that we have some ridiculously complicated pages like > map features which are not only hugely complicated with masses of > templates but also get changed very frequently. Jokes aside - as my "other hobby" I'm involved with a browser game and they have their own Mediawiki describing the areas you can go to and the items you can collect and things. A typical page is here: http://www.fwwiki.de/index.php/Rovonia - it uses about 40 templates. Some of them are very magic and set some variables that are used on almost every page. I recently changed one of these variables in one template, bringing down the whole Wiki for about two hours ;-) So yes, MediaWiki is crap, especially when used by computer geeks who tend to actually use the templating features. What options do we have? Close down the Wiki? Replace it with another Wiki software? Look for hardware/money to throw at the problem? Perhaps we would produce a nightly dump into static pages that could then be indexed by google et al? Bye Frederik _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
