The subject says it all, and it's in the perldocs, but I guess I was lazy. I thought I could get away with just having little db files around, and I know that I could just use a packed value, or a bitmap, or whatever, but then I may as well just use a bdb directly! ugh, I guess I'll look at sqlite.

So this weekend I actually got some code out on pkgsrc-dashboard and I'm pretty happy with it. Well.. almost. :) Obviously, this first commit is just something to try out and see what happens, but basically the server-side of things is starting to take shape. (I'll add a simple client very soon) It has shown some, in my opinion, weaknesses with the tools available and I'm hoping to be able to improve that situation, or at least highlight these weaknesses enough to where they are improved. One obvious example is that NetBSD doesn't include a very featured http client by default. can do http requests, but it lacks the ability to POST, set headers, and other things that would make simple web-based automation a little easier. For now, I've programming pkgsrc-dashboard to handle GET's with parameters, but it would have been easier with curl as a client target. Regardless, I'm happy with the progress I made this weekend.

So this weekend I actually got some code out on pkgsrc-dashboard and I'm pretty happy with it. Well.. almost. :) Obviously, this first commit is just something to try out and see what happens, but basically the server-side of things is starting to take shape. (I'll add a simple client very soon) It has shown some, in my opinion, weaknesses with the tools available and I'm hoping to be able to improve that situation, or at least highlight these weaknesses enough to where they are improved. One obvious example is that NetBSD doesn't include a very featured http client by default. can do http requests, but it lacks the ability to POST, set headers, and other things that would make simple web-based automation a little easier. For now, I've programming pkgsrc-dashboard to handle GET's with parameters, but it would have been easier with curl as a client target. Regardless, I'm happy with the progress I made this weekend.

So this weekend I actually got some code out on pkgsrc-dashboard and I'm pretty happy with it. Well.. almost. :) Obviously, this first commit is just something to try out and see what happens, but basically the server-side of things is starting to take shape. (I'll add a simple client very soon) It has shown some, in my opinion, weaknesses with the tools available and I'm hoping to be able to improve that situation, or at least highlight these weaknesses enough to where they are improved. One obvious example is that NetBSD doesn't include a very featured http client by default. can do http requests, but it lacks the ability to POST, set headers, and other things that would make simple web-based automation a little easier. For now, I've programming pkgsrc-dashboard to handle GET's with parameters, but it would have been easier with curl as a client target. Regardless, I'm happy with the progress I made this weekend.

So this weekend I actually got some code out on pkgsrc-dashboard and I'm pretty happy with it. Well.. almost. :) Obviously, this first commit is just something to try out and see what happens, but basically the server-side of things is starting to take shape. (I'll add a simple client very soon) It has shown some, in my opinion, weaknesses with the tools available and I'm hoping to be able to improve that situation, or at least highlight these weaknesses enough to where they are improved. One obvious example is that NetBSD doesn't include a very featured http client by default. can do http requests, but it lacks the ability to POST, set headers, and other things that would make simple web-based automation a little easier. For now, I've programming pkgsrc-dashboard to handle GET's with parameters, but it would have been easier with curl as a client target. Regardless, I'm happy with the progress I made this weekend.