lighttpd

Mono + FastCGI

January 23rd, 2008

Reggie pointed me to the FastCGI support for Mono. For our lighttpd they have a full featured page that should cover all possible configuration needs.

Feel free to try it out and comment on this article if it works as expected.

2 Responses to “Mono + FastCGI”

  1. Amr_not_Amr Says:
    January 29th, 2008 at 07:50 AM This is so nice .. but does this work with lighttpd 1.5 ?
  2. M. David Peterson Says:
    February 2nd, 2008 at 11:04 PM @Amr_not_Amr, > but does this work with lighttpd 1.5 ? Yes, though the configuration process is different, and you need to use the spawn-fcgi script to spawn the fastcgi-mono-server2 instance. The only problem I have run into thus far is that when you pass extended paramaters to the fastcgi-mono-server2 process using spawn-fcgi it seems to break the ability to launch multiple fastcgi-mono-server2 processes. For example, 
    
spawn-fcgi -s /nuxleus/Data/aspnet-fastcgi-amp-beta -f "/usr/local/bin/fastcgi-mono-server2 /maxconns=1024 /maxreqs=1024 /multiplex=True /applications=/:. /root=/nuxleus/Web/wwwroot/beta.amp.fm /logfile=/nuxleus/Log/amp.fm-beta-fastcgi.log /nonstop=True" -C 5 -P /var/run/spawn-fcgi-amp-beta.pid
    doesn't launch 5 processes as would be expected. Anyone happen to know why that might be? As far as the configuration is concerned here's what the the Mono specific pieces should now look like, 
    
$PHYSICAL["existing-path"] =~ "\.(aspx|ashx|ascx|asmx|soap|rem|asd|cs|config|dll|op|omx|php|page|rb|py)$" {
        proxy-core.allow-x-sendfile = "enable"
        proxy-core.protocol = "fastcgi"
        proxy-core.backends = ( "unix:/nuxleus/Data/aspnet-fastcgi-amp-dev" )
        proxy-core.max-pool-size = 5
    }
    Where proxy-core.backends = ( "unix:/nuxleus/Data/aspnet-fastcgi-amp-dev" ) matches the Unix pipe from the spawn-fcgi process. You'll also need to add, 
    
                                "mod_fastcgi",
                                "mod_proxy_core",
                                "mod_proxy_backend_http",
                                "mod_proxy_backend_fastcgi",
    to the server.modules section of the config file. You'll also want to be sure to add .config to your static-file.exclude-extensions directive, static-file.exclude-extensions = ( ".php", ".pl", ".fcgi", ".config" ) As far as the multiple processes are concerned and setting aside the issue with spawn-fcgi, I still haven't quite figured out how to specify to lighty that there are multiple unix pipes and what they are. This isn't a problem with 1.4.x: You can pass the proper command line params to bin-path (e.g. "bin-path" => "/usr/bin/fastcgi-mono-server2 /maxconns=1024 /maxreqs=1024 /multiplex=True /applications=/:. /root=/nuxleus/Web/wwwroot/beta.amp.fm /logfile=/nuxleus/Log/amp.fm-beta-fastcgi.log /nonstop=True", and lighty handles balancing the load between each generated pipe. If anyone has an idea of how to address the above it would be *much* appreciated.

Sorry, comments are closed for this article.