Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Tue, 5 Apr 2005 12:35:27 -0700
From: Greg Stein <gstein@lyra.org>
To: dev@httpd.apache.org
Subject: Re: simple-conf branch
Message-ID: <20050405193527.GA17108@lyra.org>
Mail-Followup-To: dev@httpd.apache.org
References: <s250fcd9.018@sinclair.provo.novell.com>
 <6.2.1.2.2.20050404130215.051861e0@pop3.rowe-clan.net>
 <20050404220134.GC14955@lyra.org>
 <opsorequdbrf0xls@ganesha.library.cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <opsorequdbrf0xls@ganesha.library.cornell.edu>
User-Agent: Mutt/1.4.1i

On Tue, Apr 05, 2005 at 08:38:44AM -0400, Paul A. Houle wrote:
>...
> 	There are good operational reasons to split up configuration in 
> 	different  files -- if the Apache install can encourage good practices,  
> based on the  decade of experience we've had with it,  that's a good thing.

You have a complex series of sites and a deep understanding of
configuration and sysadmin issues to keep it manageable. For somebody
*new* to this, they need the utmost simplicity. Even a strong sysadmin
needs something simple so they can figure out what they're working with
and then blend that into their environment.

If we shipped a setup similar to yours, most people would cry with
frustration trying to figure out where to turn this or that knob.

Documentation to help people with configuration issues and ideas can
easily be provided for admins who have moved past the "single static file
website". We already have a lot of documentation. Admittedly, it doesn't
describe scenarios like yours, but I'll venture to guess that you're in
the few-percent case. I'm more than happy to have our doc folks
concentrating on the other 97% :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/