Project

General

Profile

Actions

Fastcgi on lighttpd » History » Revision 2

« Previous | Revision 2/8 (diff) | Next »
Pieter Libin, 10/29/2009 02:39 PM


h1. Fastcgi on lighttpd

h3. Opensuse config

  • On Opensuse the lighttpd is in the factory tree at repos.opensuse.org http://repos.opensuse.org:/http/SUSE_Linux_10.1/i586/lighttpd-1.4.15-6.1.i586.rpm
  • Store the wt application in /srv/www/cgi-bin /srv/www/cgi-bin/helloworld.fcgi
  • Opensuse lighttpd configs are modular - create a new file /etc/lighttpd/conf.d/helloworld.conf fastcgi.server += ("/helloworld" => ("helloworld" => ("socket" => "/usr/wt/socket", "bin-path" => "/srv/www/cgi-bin/helloworld.fcgi", "max-procs" => 1, "check-local" => "disable", "bin-environment" => ("FOO" => "bar") ) ) )
  • in /etc/lighttpd/modules.conf
    enable the following (existing) section

    ##

    FastCGI (mod_fastcgi)

    ##
    include "conf.d/fastcgi.conf"

    : append an include line at the end of the modules.conf file

    include "conf.d/helloworld.conf"

  • When done you can access the application on htpp://your.server/helloworld

h3. Flat File Config

If you have a single config file, add such a section

server.modules += ( "mod_fastcgi" )
fastcgi.server += ("/helloworld" =>
("helloworld" =>
("socket" => "/usr/wt/socket",
"bin-path" => "/srv/www/cgi-bin/helloworld.fcgi",
"max-procs" => 1,
"check-local" => "disable",
"bin-environment" => ("FOO" => "bar")
)
)
)

  • When done you can access the application on htpp://your.server/helloworld

h3. /usr/wt

The fastcgi socket has been put into /usr/wt/socket because the default wt build does put its own session server sockets as $prefix/wt/run/server-$X. There is no requirement to let the lighttpd precreate fastcgi wt servers to handle different connections as wt will schedule server creation and session scheduling internally. The internal creation of session servers is not logged to httpd log (where it should be).

Updated by Pieter Libin over 14 years ago · 2 revisions