Over the last evenings I helped several lighty users to tune their application stack. Instead of telling the same story over and over again I wrote it down into a wiki page:
https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_PerformanceFastCGI
Over time this will be the main source for application tuning, hints and secrets.
It has been about 5 months since the first announcement of XCache. But many of you may still wonder how XCache “looks” like. So i’ve spent some hours and finally setup Administration demo page and Coverage viewer demo page
XCache was stable (the cacher stufs), but now becomes more stable (installing, configuring), and seems a bit hot recently if you may google for “php” +”xcache” :)
Thanks for your support and encourage, XCache will goes on and on..
In mod_cml is dead, long live mod_cml I gave some hints about mod_cml going to die soon. With lighttpd 1.4.12 there will be a new module called mod_magnet can attract every request and decide on its further execution.
If you want you implement most of our current modules via mod_magnet, e.g.:
A new pre-release has been uploaded with more fixes than the last release and with a new, hot module: mod_magnet . It is the promised replacement for mod_cml.
Update replaced r1303 with r1309
The forum just got migrated to the new lighty-server. As long as the DNS is not update and as fallback, the old lighty server is proxying to the new host.
As a side-effect, registering a account in the forum works again. The trac on the new host also sends out notifications on ticket updates again.
The 1.4.11 release need a maintainance package. This pre-release is taking the 1.4.11 code and fixes:
and adds:
bsdtalk061 - Interview with lighttpd developer Jan Kneschke
Thanks to Will (bitgeist) for doing the interview.
BTW: sorry for my bad microphone.
… oh not again.
The Docs are now in the wiki instead of a dead, boring manual, see https://www.lighttpd.net points to the new location already. If you want, the docs are editable for everyone now. It is an easy way to improve the docs, check if they are right, fix typos, rephrase the wording, add more examples, …
Thanks go to hoffie and the others who helped to move the docs to the wiki.
Just a short one: Handling for HTTP/1.1 Expect: 100-continue has been
added. With the new infrastructure it was only a few lines to get it in.
curl and some WebDAV clients were using it to verify that the server
speaks HTTP/1.1.
I’m not completly sure yet how I will add the spawning of processes to the new mod_proxy_core. The current idea is mod_spawn described as below. If you have specific needs or ideas how to implement it, add your comment please.