Re: [Nagios-db-devel] pgwrapper and other stuffs

[Matthew K. <mk...@ma...>]

On Tue, 2005-23-08 at 21:18 +0200, Andreas Ericsson wrote:
> Matthew Kent wrote:
> > Hey Ben, just looking at the pgwrapper stuff you added a while back and
> > I think it's great and exactly what the mysql implementation needs as
> > well. Have you happened upon a similar implementation for mysql?
> > 
> > I'm thinking I'll write one and draw up a new version of my neb based on
> > mysql 5.0 so I can use triggers and stored procs this time around. Plus
> > I figure by the time I get a good interface together MySQL 5 will
> > probably go from beta to stable anyway :)
> > 
> > On the interface front I really never did find a suitable framework for
> > recreating a better version of the nagios cgis in PHP. The time
> > investment to create one properly from scratch was just too much (partly
> > because I'm not fantastic with php in the first place). So I've been
> > learning ruby for the past couple months with the goal of writing it in
> > ruby on rails. Ideally it should keep me from having to write the nitty
> > gritty stuff like authentication, caching and template support and focus
> > more on presenting the data. 
> > 
> > Has anyone listening on this list developed with ruby on rails and is
> > interested in helping?
> 
> 
> Can't say that I have, but we might be able to give you a load off from 
> that anyways though.
> 
> We'll be developing a GUI with everything and sugar on top, and we'll 
> most likely base it on one (or both) of the database modules.
> 
> We in this case means OP5, the company I work for. The resulting code 
> will be GPL'd and released to the public.
> 
> Incidentally, we're also looking for developers (C, Perl, PHP and SQL 
> mainly, with some shell and possibly Python thrown in for good measure). 
> Interested?
> 

Oh cool, that's good to hear.

I'll work on getting the mysql module up to par and see how close I can
get to unifying the views and stored procs to match the postgres module
(with the goal being to make any future interface abstraction easier).

I'd be more than willing to help with any database work, but since we
are switching to ruby on rails at work it's in my best interest to spend
my free time learning about it for now. 
-- 
Matthew Kent <mk...@ma...>
http://magoazul.com