Last time i looked at Hiawatha there was a post on the forum where the owner was saying he was going to stop development. (to lazy to look for the post)
Have used Cherokee in the past it was good not sure what its like now with its new version 1.2.x i used it back when it was 0.10 or something.
Chris that was just closing the website, not the project. :0
I think both the Hiawatha and Cherokee team just released new updates last month so if they did stop development somebody is still pushing updates.
Lighttpd on the other hand, well read for yourself:
User Wrote:What is happening? No blog updates, what so ever?
Have we given up competing against Ngnix?
Dev Wrote:Yes.
User Wrote:Is that an official statement?
Dev Wrote:As "official" as your stupid question.
...
Why should we change something if you don´t report bugs or submit enhancements?
(
Source)
Hiawatha. The few times I've tried things other than Apache, Hiawatha has always stood out for me. Of course, with some of the content I serve, I'm pretty much restricted to Apache because its the only one that has all the options I use without a lot of extra work to get them going.
I found out that Cherokee is being maintained in Arch Linux's community repo so that might be the best bet since it will stay updated versus user repos. Currently fighting with VirtualBox to get the VMs working properly for testing.
I would like to hear any feedback about this as well.
I haven't installed Hiawatha yet (and don't think I plan on it TBH). I really like Cherokee and I even got my partner hooked on it so we'll probably be using this for our production web server in the near future. I am still doing some playing around with it on my VM but I'm reading the document page-by-page and really like the cherokee-admin, I was afraid I wouldn't like it because it's a GUI but I was wrong. Easy to configure and really secure. It just works right out of the box. The Cherokee Market is nice but the only thing in it that I will use is phpMyAdmin (which was easy to install). I like how you can backup and restore your configurations on the fly (the backups are stored on their servers so you can restore the configurations to any Cherokee server by just logging in with your Cherokee Market account in cherokee-admin).
I should mention that even though the Arch Linux community repo shows Cherokee 1.2.2, pacman actually installs 1.0.5 for some reason. I just downloaded the tar.xz and installed it manually (which I found out that Cherokee has a 3 second install option which is only one command so I took the long route).
I am still getting used to it but right now I'm at the point where I'm either going to go with Cherokee or just go back to Apache for my personal site due to it being what I am most comfortable with. I don't foresee any reason why I wouldn't go with Cherokee but I want to do as much testing as possible before I decide to rebuild my web servers.