FastCGI, SCGI and ajp in lighttpd 1.5

[stephan]

I propose an addition to the documentation to be ready for lighttpd 1.5.

Lighty 1.5 completely drops mod_fastcgi and adds mod_proxy_core and backends for scgi, fastcgi and even ajp, so the documentation has to be adjusted accordingly.

This little code snippet will proxy requests coming to www.example.org to a django app which has a unix socket at /tmp/django-myproject.sock

$HTTP["host"] == "www.example.org" {
  proxy-core.balancer = "round-robin"
  proxy-core.protocol = "scgi"
  proxy-core.check-local = "disable"
  proxy-core.backends = ( "unix:/tmp/django-myproject.sock" )
  proxy-core.max-pool-size = 5
}

• proxy-core.protocol should match the protocol setting from runfcgi
• proxy-core.backends should match socket/host-port setting from runfcgi
• proxy-core.max-pool-size should match maxchildren from runfcgi

Maybe runfcgi should be dropped and added to runserver. However, calling runserver without arguments would still spawn the development server.

After lighty 1.5.0 is released we should do some benchmarks on performance of fastcgi/scgi/ajp, try different load-balancers and determine whether forking or threading is better on different setups.

References

​http://trac.lighttpd.net/trac/wiki/Docs%3AModProxyCore

[anonymous]

Updating the documentation for something that hasn't been released yet would be premature. We aren't going to magically drop all support for people using version 1.4 when that happens, in any case.

Closing this as wontfix for now. We can revisit it when/if lighttpd 1.5 is released.

[Michael Radziej <mir@…>]

Please don't close tickets anonymously (though your reasoning appears to be sound).

[stephan]

I agree, let's consider this when it's the right time.

[Malcolm Tredinnick]

Sorry, Michael, that was me in comment #2.

(Grrr... it would be nice if it wasn't possible to accidently do stuff anonymously or have persistent logins or something. :-( )