Sorry, I haven't been following the thread very closely, but this caught my attention.

 

The Apache config solution described below isn't viable with the current setup.  The reason for this is because we aren't using Apache Virtual Hosts in the standard way.  Instead, we are using mass virtual hosting (http://httpd.apache.org/docs/2.2/vhosts/mass.html), which has worked to this point because all the wikis have been using the same Apache settings.  To do something like what is described below would break that model, which would be a very big pain in the neck.  In addition, it wouldn't be quite zero maintenance, as it would require a reload/restart of both Apache servers to take effect.

 

An alternative solution is to use .htaccess for the rewrites, which opens its own can of worms.

-Matt

>>> Frank Sundermeyer <fs@suse.de> 7/27/2010 8:45 AM >>>
>On Tue, 27 Jul 2010 16:16:48 +0200 Marcus Rueckert wrote:

>Hi,

>> On 2010-07-27 15:23:32 +0200, Frank Sundermeyer wrote:
> >> On the other hand cluttering up the new wiki with 1000+ redirect
> >> pages is no option, too, because it will bring back chaos to the
> >> new wiki.
>>
> >using redirect pages is much better than cluttering 1000 rewrite rules
> >into apache. because we cant edit the later easily.

>to create the apache redirects we simply need a script that gets a list
>of all pagenames from the category "Transfered Articles" in old-en,
>fetches the MediaWiki sources and grabs {{TransferNote|<TITLE>}} from
>each source to generate a Redirection list.

>Run that script by cron and let it output a file that is included by
>the apache vhost config and you have a zero maintenance solution.