How did I not know about this sooner?
Trying to build a particularly large maven project would consume so much CPU that my poor laptop would quit because it was sweating too much.
I used schedtool to set an affinity to only one of the two CPUs available on my dual-core laptop for the shell I used to launch the build, and voila! Things don't get as hot, and my system stays responsive. *phew!*
I really really like MonkeyGTD for trying to get my crap in order. I devided to try chrome on gentoo linux, and picked up/found a good ebuild to grab the latest beta, but Chrome won't allow saving to local files by default.
I have to say that updating RoR for old apps always lands me in some wonky funny business: missing config variables, moved whatsits and thingummies. grr. The issues aren't easy to search for, either.
Some (a few here and there) spam bots have been leaving comments lately... good thing that there was already a reCAPTCHA plugin available for nucleusCMS: had I known that earlier, I would have switched over earlier!
*sheesh*
bonus: one nagging/back-of-the-head item knocked off the list early in the new year...
So. The last time I migrated the blog, I got about 1/2 the job done. I liked Nucleus CMS (which I used for Dad's blog), and got that set up, but I wanted tagging, rather than categories, and just never had time to get the plugins I could find that would do that working quite right.
But now, I have it! I (heavily!) refactored some plugins created by other people: i.e. I cut out just what I needed, and simplified from the "everything and the kitchen sink" to as bare bones as I could get. And it all works now. Shiny!
I really do like Nucleus as a blog engine thing: I've yet to find anything I couldn't make it do using plugins-- with every other bit of blog software I've played with, I've had to hack the source, which made upgrading a royal pain. I still haven't brought in a markup language like textile or markdown-- when I migrated from textpattern (which was migrated from MT), I just pulled the HTML version of the posts into the table. From a migration point of view, this makes sense, as the full HTML is the only thing that doesn't change (it's a pain to go back and edit, but how often to you edit really old posts? like never!). I'm confident that a plugin can do what it has to (maintain the textile/markdown in a different table than the entry), it's just a matter of getting to it.. *sigh*
