So because for now, our Mumble services are hosted on a pretty crummy server in terms of RAM, I decided to use that as the catalyst for playing with lighttpd. Murmur hosting uses almost no resources except bandwidth – you could probably host a couple thousand servers on a Celeron with a fat enough pipe, but our control panel at the moment utilizes PHP and Apache which takes a little more “oomph” so to speak.
So I setup lighttpd, and finally made PHP/Ice work with it after some initial permissions troubles, and the results are amazing. I shaved a good 100MB of RAM off (leaving us with plenty of room for more Mumbles) and the pages load much snappier (which is funny because I’d always figured that mod_php would blow away fast-cgi any day of the week). I’m really pleased with it.
I also last night added a log browser function to the Mumble control panel, but I’m having some troubles with the getLog() function behaving appropriately, so the result is buggier than a New York City hotel.
I’m pretty confident I can dig into the Murmur code and figure out what I’m doing wrong and make it all neat and working correctly. I still probably want to do a channels and ACL editor, as well as a page to configure the certificates (because I’m sure *someone* out there will have free certificates and want their Mumble to be verified) and then clean up things like password changes and whatnot. I may add a “lost password” feature too, but I’m not sure how to do that – that might be a function for Sabrienix’s ticketing system instead.
But yeah, from an Apache fanboy in excess of a decade – thumbs up for lighttpd.
I hope you get it all worked out. It can be such a pain when things like this happen. I have no clue about most of it.