> Looks like it depends on distribution, in my Archlinux /etc/httpd/conf
> has only httpd.conf as in default apache distrib, but different vendors
> do local customizations. We just need to come to some solution and make it.
The single well documented config file is the best starting point, anyway
really? isn't the opposite the case?
on all my SuSE boxes there's a main config file including the others.
think this is so for a long history of releases.
so all of these server management tools just need to create separate
config files, e.g. for virtual servers, to add new entries, e.g.
Look
> Apache used to have different .conf file but then merged into one
> httpd.conf.
really? isn't the opposite the case?
on all my SuSE boxes there's a main config file including the others.
think this is so for a long history of releases.
so all of these server management tools just need to create
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
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 h
Looks good. Especially the "logs" dir as a central place for logs is nice.
Where is man? (or doc)
doc/ and/or man/ should be installed as well
Would be nice to have it! Including mimetypes in a tcl file is more visible
than only in the c-code. I also have a list of types, but not as long as
Hi Vlad,
> /usr/local/ns
>bin
>conf
>include
>lib
>html
>tcl
>logs
>modules
Looks good. Especially the "logs" dir as a central place for logs is nice.
Where is man? (or
