High-Tech Rojak

If you installed Plone 3.x from their universal installer, there is a default buildout.cfg provided. Edit this to installed cool additional packages and just run `bin/buildout`. It will download whatever you need and then ready to be up and running again. The buildout will override your zope.conf so if you want any settings to persist in your zope.conf it should be put into your buildout.cfg. Inside the buildout.cfg there is section for client1 and client2 if you installed the default cluster settings. So to configure the effective user for client1 (so that root can start the instance) you should add: effective-user = plone in the client1 section. And inside client2 section you can just add: effective-user = ${client1:effective-user} so that you don't have to edit at 2 places later. And do you want to enable webdav with that? Then just add: zope-conf-additional = enable-ms-author-via on <webdav-source-server>

I've always considered myself more of a coder than a documenter (if there is such a word). I like writing codes but I hate writing about them. I do write about it once in a while in a blog or something if it's something especially hard and I might have to refer about doing it again but usually I'll just file it in my head as "ooooh.. I can look it up later if I REALLY need it". So some of the stuff that I really hate to write up are user manuals and requirement specs. Now I've been burned enough times to know that requirement specs are really crucial to a successful software project. If the user does not know what they want, then you'll soon be sucked into the black hole of "user wants" pretty soon and it would take a whole lot of thick face justifying yourself just to save your sanity much less the project. But even then, I'm still very much unmotivated to do it. One of the reasons is that it is so bland and boring. Boring to write, boring t

I'm a Fedora ambassador, I recommend people to use Ubuntu, but I myself use Arch Linux. I'm not sure what that makes me.. :P But I love using Arch. It is lean, mean and geared towards the more tinkering inclined in the sense that almost everything is default and you have to hand configure yourself... with a text editor :D So it was really sad for me last week to read that they are going to drop support for the i686 . For a whole week I was contemplating which distro would I go to now? I really like Arch's way of a rolling update. Not waiting for a certain dateline but get the newest thing as soon as it's ready. But after reading that news I am concerned because I don't think my laptop support x86_64 (Haven't tried it yet though, but it's a really old laptop). And not only that, if one day I am fortunate enough to get myself a netbook of my own, I doubt those small atomic chips support 64bit either. So where should I go? My choice was 2. Fedora or Ubuntu. I h