[EMAIL PROTECTED] wrote: > > [Garry Glendown] > | > | Why not just keep it plain CGI (easy to port), add a couple of gfx and > | use the server side to access plain flat files ... we're talking about > | server CONFIGURATION mainly, not administration ... the latter may be a > | nice add-on later, but the main goal should be an easy to use interface > | to Apache configuration ... compile it, run "make install", start up > | httpd and configure the whole server ... > > seen from this point of view I think the most productive first step > would be to start off with a server config generation system and > perhaps model it from that. > > how can the config be divided up? what pieces of config are relevant > to show on the same screen etc? > > I have usually divided it into 3 parts:
In March, when I started work on the concept, I wrote up a little doc describing some basic functions of the config GUI ... it's available on my server (http://acg.regio.net) in the internal part ... also, unter /config, a little design study of the basic interface can be found ... -gg
