On Sat, Sep 25, 2004 at 10:23:40AM -0600, Brad Nicholes wrote:
I am in total agreement in fact my guess would be that most
organizations will eventually split up the httpd.conf file to fit
whatever needs they have. But I would imagine that no two organizations
split up the .conf file in the
I'll throw in my two cents.
As part of a large multi group organization (that I am sorry to say does
not get along all that well) I have, for security reasons, split up our
configuration file into about 20 seperate files. Certain people or groups
have access to certain things that I am
Therefore I think there are certainly valid reasons to split up the
conf
file, and from a usability perspective, it may be a bit more
confusing
upon an initial install, but the benefits down the road were immense
for
me. Mind you, being in an organization where 12 people of varying
degree of
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
What I've tried to do:
- Strip httpd.conf to only the config directives that almost everyone
needs to worry about.
- Put everything else in an extra/ directory, with commented-out Include
directives
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to move.
Any reason the Netware MPM part cannot be removed from near the top?
On Fri, 24 Sep 2004 13:12:30 -0400 (Est (heure d'été)), Joshua Slive
[EMAIL PROTECTED] wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
it looks good to me; I guess all those little pieces need
extra/foo-std.conf so that users will pick up
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to move.
Any reason the Netware MPM part cannot
On Fri, 24 Sep 2004, William A. Rowe, Jr. wrote:
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good. I think this is a good direction to
At 02:27 PM 9/24/2004, you wrote:
On Fri, 24 Sep 2004, William A. Rowe, Jr. wrote:
At 01:08 PM 9/24/2004, Paul Querna wrote:
On Fri, 2004-09-24 at 13:12 -0400, Joshua Slive wrote:
A straw-man proposal for a new config organization is at
http://www.apache.org/~slive/newconf/
Looks pretty good.
Maybe I am jumping in here out of turn, but let me ask the obvious
question. Why would we want to split the standard base httpd.conf file
up into multiple files? Doesn't this end up just confusing the average
user? One thing that I always tell new users of Apache is that rather
than trying
On Fri, 24 Sep 2004, Brad Nicholes wrote:
Maybe I am jumping in here out of turn, but let me ask the obvious
question. Why would we want to split the standard base httpd.conf file
up into multiple files? Doesn't this end up just confusing the average
user? One thing that I always tell new
11 matches
Mail list logo
