Symbiosis is wonderful
Symbiosis is basically a collection of configuration snippets, code, and libraries which works to offer virtual hosting in a reliable consistent and easy to understand fashion.
You implement hosting for a new domain by merely creating a directory tree. So for example you might configure the hosting for the domain example.com by running:mkdir -p /srv/example.com/public/htdocs echo "hello, world" >> /srv/example.com/public/htdocs/index.html mkdir -p /srv/example.com/mailboxes/webmaster echo "super-secret" > /srv/example.com/mailboxes/webmaster/password mkdir -p /srv/example.com/config echo "3l33t" > /srv/example.com/mailboxes/config/ftp-password
There you are, now http://www.example.com/ and http://example.com/ will work, and you may login to check mail with the email address firstname.lastname@example.org via POP3, IMAP, IMAPS, or POP3S. Finally you can FTP with username example.com and be dropped into the public directory.
The mail handling is very flexible, and the webhosting supports wonderful things.
I don't generally talk about work-stuff explicitly, but we've just made a major new release of the Symbiosis system such that it works upon Squeeze and has lots of IPv6 support out of the box. (Email, DNS, HTTP, Firewalling, FTP etc.)
All in all it is simple, well-documented, and open-source with a reasonably large user-base. More external testers, users, and developers would be a wonderful thing..
Mutt Mailboxes & Idle Hooks?
Mutt is wonderful but I'm starting to get annoyed by its lack of auto-mailbox discovery.
Assuming you use procmail you might deliver mail to ~/Maildir/.foo/ and mutt won't notice that if the directory is created once it starts.
(This is because generally mailboxes are defined via "mailboxes =one =two ..", even if you use a shell snippet it won't get updated unless you re-read configuration, or re-exec mutt).
I wish it were possible to use inotify/dnotify/something magic such that everything beneath ~/Maildir would just work.
(Re-reading mailboxes manually is one solution but it is .. nasty?)
I'm thinking that of all the possible solutions one of the most potentially interesting would be to define a new hook: "idle-hook command .."
That way "command" would be executed every time the client is idle. (This is a distinct state unrelated to IMAP IDLE times.)
Nopte: There is already "mail_check" & "timeout" options. Even running a defined command immediately following the code for mail_check would be reasonable.
I continue to use, love, and enjoy my node.js-based reverse HTTP proxy, and pub discussions seemed to suggest it is a great idea (due to flexibility) but it will never take on because people don't trust node.
I'm almost tempted to re-code it in LUA & C. But I can't help but think that would be a waste of time which would not increase adoption - after all most people use "simple" reverse proxies, and they are well suited by Apache, nginx, or even varnish.
Still no rush I suppose.
In more personal news after living in this flat for 7 years, or so, I'm getting a new bathroom designed and deployed. Good times.
In the meantime I've been steadily watching Stargate SG-1 having recently purchased a box-set of series 1-10. I've just started series six this evening, and I'm enjoying it a lot.
ObQuote: "You have been recruited by the Star League to defend the frontier against Xur and the Ko-Dan armada. " - The Last Starfighter (1984). First film I ever saw at a cinema as a child.