Apache used to have different .conf file but then merged into one
httpd.conf. Multiple config files may not be easy to maintain and configure.
Bernd Eidenschink wrote:
Hi Vlad,
Agree, some directory (like contrib/) with all examples and startup
script would be good to have. Also, similar to postfix, example config
with description for each parameter can be provided, but runtime config
during installation would have only needed parameters.
yes, postfix has a well documented main.cf file. maybe something
apache-like would also work: one file, explaining config structure and
including (sourcing) other parts, like "listen.conf", "modules.conf",
a vhost-config directory where all virtual host files ending in .conf
are sourced, mime.conf, database.conf, threads.conf, things like that.
finally, in an RPM, we could manage a structure like:
/etc/nsd/nsdconf.tcl
- listen.conf
- mime.conf
- threads.conf (or performance.conf ...)
- modules.conf
vhosts/
www_example_com.conf
www_elpmaxe_com.conf
...
just a thought.
-Bernd
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
