--- Ray Olszewski <[EMAIL PROTECTED]> wrote: > > Actually no. I meant people other than Erich who are either upstream
> developers (e.g., Tom) or packagers (e.g., Charles). That is, the sorts of > people who will actually have to use, or to ignore (as they have up to now, > saving the occasional e-mail), whatever gets implemented. But any thoughts > from the old development team would be great too. I don't know if you want to hear from someone who was hoping cdb would take off, but had to do a web-based configuration UI on bering anyway.. but here goes. I would have prefered to use cdb, /if that's what was mainstream/ but it was in early development when we started working on our UI, and then it got ignored. What we ended up doing was writing shell scripts that directly modify the configuration files themselves, and have the smarts to look for "related" packages to grap what the web-script needs. (e.g. dhcpd has to look at interfaces to figure out which interfaces it could serve dhcp addresses on) In a few cases, we source "foo=bar ..." files. (but from experience, I can count the number of variables that we need to store this way on one hand.) The biggest headache so far has been dealing with the case where the web-based script makes a change, and then a custom tweak is made afterward. Generally, our configuration files have comments in them that read: #vvvvvv managed by web interface do not edit below this line .. #^^^^^^^ managed by web interface do not edit above this line and then have the script just spit out everyhing above and below the markers, managing only what is inbetween. So far its worked as a fair compromise, but our userbase either only uses the web interface, only uses ssh, or wrote the web-script and knows how to tweak things. :-) It works as an "advanced home router" for the web case. I'm not at liberty to give the whole web thing away, but if anyone is interested I could peel off a few cgi's as a demo. But, as an integrator (sitting between user and developer) I would have preferred to use the cdb approach, but don't want to have to be the one to define the cdb database/heirarchy, etc. for all of the packages. If there was some consensus of what goes in the database and who puts it there, I'd be happy to use it. hope this helps. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
