Hi !
In the process of a spring-cleanup I wanted to attack
the gobal sample-config.tcl file that we deliver
with the server. The purpose of that file is obviously
dual:
o. get a config file people can start with
o. declare and document each and every config option
As it seems, we fail to meet any of those goals _really_.
One can use this file to start the server, right, but
thats about it. Any attempt to understand it, is not
going to bear fruits...
I will reorganize this file as follows:
o. write man page about the overal layout of the file
o. write man page explaining server internal parameters
o. expand man pages for each module and put explanations
of module paramaters there
o. rewrite this file to include sample for configuring
two virtual servers
Since we now have man pages in place, logical place to
put all possible documentation and description of options
is there. In the config file we can put only really necessary
stuff that is needed to startup some example configurations
and put cross references to the documentation.
Vlad already started this right by providing a minimal
no-fuss config file for somebody that needs to pull up
the server fast with minimal config. What we need is
something similar to that for virtual servers in perhaps
2 or 3 sample configurations. But we should NOT put docs
in that files. We should write docs in man and put only
refs to that in the config files.
Any other ideas? Suggestions?
Zoran
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
