We've never had a great monitoring solution. If something goes really wrong, usually I wait for someone to text me if I'm not there to deal with it. I've long wanted to initiate an automatic notification of downtime, and tried to use something like nagios to do the monitoring, but it ended up being overkill for this monitoring of 1 service on 1 server. So I decided to write my own solution.

I believe there may be some logical complications here, so I wanna talk out my logic and ask you, the readers, to poke holes in my thinking. This script isn't done yet, by far.

IT'S FINALLY COMING! THE SERVER IS SCHEDULED TO BE DELIVERED TODAY! This will be an ongoing chronicle, full of pictures and such, showing what we're doing to ready this thing for production. It will not be a quick process.

No new news...but I saw a ton of traffic to the server script posts, so I wanted to make a place to get all the scripts without me having to edit posts all the time. So I made a new page, http://owner.teh3l3m3nts.com where the scripts will be auto-updated as I upload them to ftp. Carry on folks :D

WOOO CONGRATS TO BOUKE! NEW ADMIN! WOOO!

As I pointed out last week, we use a generic server-start script. That needed to go. It was built to accommodate a bunch of different configurations, but we use a very specific configuration. To that end, I've re-written the script, and commented it out like a good little coder should do.