hoffies blog

Yesterday I wanted to set up mailman… and have still not been able to get it working. This server is completely messed up. I’m running SysCP (patched for lighty support) and now I realize that it’s overkill for me. I have 7 “customers” in SysCP while 5 of them are mine… I have absolutely nothing against SysCP, it’s a nice tool for webhosting, but for me it has just become annoying. The lighty config file with my custom changes grows and grows and it will probably be longer than the automatically generated one by SysCP once… that doesn’t make sense. The only reason which made me keep using SysCP was the mail setup (postfix + courier-imap using mysql) because I hardly had any knowledge about it. I don’t claim to have much more now but I think I will try to replace courier-imap by dovecot and start a postfix config from scratch. Additionally I’ll kill lighty-1.4 and replace it by lighty-1.5 with external spawned fastcgi servers.

So, if any services on this server do not work in the next hours/days, don’t be surprised. :)

Maybe I can get a working mailman setup then…

As you can see at the timeline in lighttpd’s trac, lighttpd (1.5) now supports a $PHYSICAL[“path”] conditional. And this is very useful, especially for automaticly generated config files like in SysCP or an external lighttpd directory-level config parser (I have concrete ideas for it and started even implementing it a while ago, but I don’t know when there’ll be a first working version. I don’t know if someone beside me is interested in such a daemon/program, so let me know if you like the idea).

The patch (extracted from svn) also applies to the 1.4 branch.