Re: Fw: cvs commit: httpd-2.0/docs/conf ldap.conf proxy.conf ssl.conf httpd-std.conf httpd-win.conf

[Rich Bowen <rb...@rcbowen.com>]

On Tue, 16 Oct 2001, William A. Rowe, Jr. wrote:

> Relevant suggestions for all apache-docco hackers :)
>
> ----- Original Message -----
> From: "Eric Hubert" <er...@gmx.de>
> To: <de...@httpd.apache.org>
> Sent: Tuesday, October 16, 2001 6:05 PM
> Subject: RE: cvs commit: httpd-2.0/docs/conf ldap.conf proxy.conf ssl.conf httpd-std.conf httpd-win.conf
>
>
> Hi folks,
>
> I don't know whether a user's estimation is valuable, but I have to
> totally agree with Joshua. I wouldn't like to look over a couple
> of different configuration files.
> It is also important to keep the httpd-std.conf as short as
> possible. Otherwise it is only scaring new users.
> Example configurations are also very useful but shouldn't mixed up
> with the httpd-std.conf.
> I'd appreciate it if the user could access sample configurations
> from the corresponding modul's documentation pages, which show how
> to use the module's directives in common contexts.
> The user can quickly find the necessary information and simply
> paste it in the appropriate section in httpd.conf.
> >>>From my point of view (and that's definitly a user's view), the
> user gets confused as more files are present in ./conf and only
> tries to start quickly without having a look into the manual.
> In the majority of cases this ends up in spending more time on
> the whole task.

Long, long ago, I started working on a Perl doohickey that would take
the standard conf file and munge it into a variety of smaller files. The
no-comments file. The only-important-comments file. The
only-section-headers file. For some reason, I never got done with those,
but I have the code lying around somewhere. I will try to pick that
project back up, now that I am starting to dig out from under a few
other projects.

Also, the comments about sample configurations is a really good idea, if
they are kept updated. In everyone's opinion, should these be inline in
the module documentation itself, or should they be in some sample_conf
directory and linked to from hither and yon. I would think that the
former would be much more likely to be kept updated.

-- 
Rich Bowen - rbowen@rcbowen.com
... and another brother out of his mind, and another brother out at New
York (not the same, though it might appear so)
	Somebody's Luggage (Charles Dickens)


---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org