This took me a little while to figure out, so I’ll blog here to help others (and me, next time I need to do it and can’t remember how).
I use the MoinMoin wiki software to run a couple of wikis and they run under the Lighttpd web server. With the current stable Lighttpd (1.4) you configure it to use the MoinMoin fastcgi service a bit like this:
$HTTP["url"] =~ "^/wiki" {
fastcgi.server = ("/wiki" => ( "mywiki" =>
( "host" => "127.0.0.1",
"port" => 22000,
"check-local" => "disable",
"broken-scriptfilename" => "enable" )
))
}
The new Lighttpd (currently in development, but to be version 1.5) has reworked the way you define fastcgi backends, and has lost the “broken-scriptfilename” option in the process. Without it, MoinMoin doesn’t see what wiki page you’re trying to visit, and can’t build new links properly. Luckily you can reproduce this feature with some proxy-core rewrites:
$HTTP["url"] =~ "^/wiki" {
proxy-core.protocol = "fastcgi"
proxy-core.backends = ( "127.0.0.1:22000" )
proxy-core.rewrite-request = (
"_pathinfo" => ( "^/wiki(/.*)" => "$1" ),
"_scriptname" => ( "^(/wiki)" => "$1" )
)
}
And your MoinMoin lives to be spammed another day.
Comments
For proxy only, better use
proxy-core.protocol = “http”
[…] to my post about getting the MoinMoin wiki system working with FastCGI and Lighttpd, here is how to do the same with NGINX. MoinMoin is configured in FastCGI mode and listening on […]