On 2004.05.07, Bas Scheffers <[EMAIL PROTECTED]> wrote:
> Dossy said:
> > AOLserver 4.0 has virtual servers built-in.  For some documentation how
> > to set it up, start here:
>
> Would it be an idea to make config simpler by including it in the
> distribution?

Maybe, for more advanced users.  However ...

> Without help fom the wiki, I already decided to create a config/
> directory with nsd.tcl and server-foo.tcl, server-bar.tcl, etc.  The
> server files have only server the specific config and the nsd.tcl
> simply finds all the server-*.tcl files and sources them.

So, you're no longer a newbie.  Congrats.  :-)

> A set-up like that in the distribution would make it easier for newbies to
> use it.

This, I doubt -- read on ...

> If you are new to the nsd.tcl file, I can imagine it to be quite a
> daunting task to set up vhosting, especialy if you don't think of using
> the seperate files and sourcing method. Wouldn't want to configure
> multiple servers in the standard nsd.tcl, especialy with the layout it's
> currently got!

Right!  However, would you really suggest that a newbie *start* learning
AOLserver by configuring virtual servers?  Or, hand them the simplest
possible config, one single file, that gets one single server up and
running with very little effort?  Then, they can study the config file,
and once they graduate from newbie to beginner, they can split out the
file into separate files on their own, as their individual needs
dictate?

For newbies, a single, annotated and quickly usable (i.e., w/ no
changes, you should be able to just start the server and watch it run)
is probably the BEST thing to start them with.  They can get a very
simple server running in just a few short minutes.  It's easy to ask
newbies to attach their (one) config file to an email to help them
troubleshoot, too.

I think a separately maintained and distributed "config pack" might be a
great idea: something that the AOLserver community could start building
and maintaining.  The core distribution should still ship with the
overly simple sample-config.tcl, but once folks are looking for a more
robust config. solution, they can go out and download the config toolkit
that has things partitioned nicely into separate files (nscp, nssock,
nsdb, nsopenssl, etc.) and configurable servers by inclusion of the
appropriate modules they need to load, etc.

Does this make sense to you?  Do you still disagree?

-- Dossy

--
Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of 
your email blank.

Reply via email to