Hi Vlad,
> I made some small changes regarding initial installation in CVS, looks
> more like Apache now but i think it is much easier. Also included now 2
> config files that can be used immediatelly being sample-config.tcl more
> documented and eventually it will include description of every con
I made some small changes regarding initial installation in CVS, looks
more like Apache now but i think it is much easier. Also included now 2
config files that can be used immediatelly being sample-config.tcl more
documented and eventually it will include description of every config
parameter.
Hi Andrew,
> Huh? I'd say the typical first-time AOLserver user needs to set up at
> least two AOLserver instances, one for his Development site and one
> for Production. This should be the DEFAULT, easiest to do setup, not
> something special that every new user has to hack in for themselves.
On Thu, Jan 19, 2006 at 09:08:09PM -0500, Vlad Seryakov wrote:
> Hi,
>
> I am proposing new directory structure for /usr/local/ns, current
> installation of naviserver comes from aolserver multi-server environment
> which is not very usual. For beginners it is very confusing, for
Huh? I'd say
> 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
Yes, that is my point, by default install in simpler structure and
provide examples of more complex setups whether in config file or other
sample-configs.tlc files.
It is just currently it is neither of two, only confusing installation
and non-complete sample config:-)))
Jeff Rogers wrote:
Vlad Seryakov wrote:
Hi,
I am proposing new directory structure for /usr/local/ns, current
installation of naviserver comes from aolserver multi-server environment
which is not very usual. For beginners it is very confusing, for
advanced users it does not matter because they customize it as t
Hi,
I am proposing new directory structure for /usr/local/ns, current
installation of naviserver comes from aolserver multi-server environment
which is not very usual. For beginners it is very confusing, for
advanced users it does not matter because they customize it as they want.
What do yo
14 matches
Mail list logo
