Re: An interface to Apache

[Garry Glendown]
|
| Why not just keep it plain CGI (easy to port), add a couple of gfx and

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:

1. general server config stuff (ServerType, ScoreBoardFile, User, Group, ServerRoot, HostnameLookups, Timeout, KeepAlive, KeepAliveTimeout, MinSpareServers, MaxSpareServers, StartServers, MaxClients, MaxRequestsPerChild, Browsermatch stuff, UserDir, Icons, general aliases, language stuff, htaccess stuff etc.)
2. per virtual server files containing a <virtualserver ip#> section with configs like ServerAdmin, DocumentRoot, ServerName, ErrorLog, TransferLog, ScriptAlias and various other tings that might apply to the server.
3. static stuff that almost never changes. (MIME stuff etc.)

then I usually create a makefile that creates the targets (config files) depending on wether any of the files that the targets depend on have been modified.

-Bjørn Received on Mon Jun 23 02:45:57 1997