|
From: Bruce S. <bw...@ar...> - 2003-06-23 19:26:43
|
> > Instead I'm writing a ncurses setup utility, because for the web > > interface, you need a network card up and running first. > > > > A web interface would be a nice addition, and a logical next step. > > > > I've VERY GLAD to see "PHP" listed above. Personally, I wouldn't > > use anything else to write the web interface. > Niether would I... Good. I was afraid a Perl monger would want to write it. :-) (I don't care for Perl) I'm also not sure that Apache is necessary. It would be nice to get by with a smaller web server that supports PHP. I don't think the web interface needs many of the advanced features offered by Apache. But, I could be wrong. I've only have experience with Apache ... > > Perhaps we could work together on the web interface? > > > I would like that.... I'll send out some ideas that I have to get one > up quickly and also be usefull... Yes. I think a first step would be to decide what should go into the web interface, what should stay in the ncurses setup, and what should go in both places. As an example, I think setting up the basic functions, like network cards, language, keyboard, etc. (stuff you normally only do once) should stay in the ncurses setup. I think setting up more advanced services (dhcpd, iptables, CIPE, ...) should go in the web interface. - BS |