httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <ra...@zyzzyva.com>
Subject Re: Per VirtualHost config files
Date Thu, 04 Apr 1996 23:35:41 GMT
I missed this mail a few days back...

> On Sat, 30 Mar 1996, Randy Terbush wrote:
> 
> > I guess I am not following this because I don't understand why
> > I would want to do it this way.
> 
> I think the problem is that you were very vauge in your original patch
> description. What you said was the patch "adds the ability to have
> separate config files for each virtual host." Which is an ability that
> already exists, as was pointed out.

Probably. It was late and it had been a rough bout with Solaris...

> What the patch actually does, at least so far as I can tell from
> reading it, is it lets you specify a directory (relative to the server
> root). This directory is scanned for files ending in ".vconf", which
> are then processed.

Yes.

> I see what you're trying to accomplish, but I think it's kind of half
> way there. I don't like the patch as it is, it's too specific yet not
> quite there. I'd either make it so that it adds the <VirtualHost> by
> itself, using the filename or something for the name
> (e.g. www.apache.org.vconf), or make it non-virtual host
> related. i.e. make a directive that scanned a directory for files
> (maybe ending in .conf - but not .vconf), and processed them. This
> might actually be useful, as there are other things you might want to
> do with that as well. Maybe you want to be able to switch some other
> directives without editing the config files, but just moving them from
> place to place. A modular config file, I think, is what you want.

This is a good suggestion. I'll make the change and resubmit.

> > What I am trying to accomplish is a config format which allows
> > me to one virtualhost by adding a single file to the virtualhost
> > configuration directory. This is a much friendlier scheme for a
> > configuration interface than having to deal with a huge file
> > with many different/unrelated directives, or one large file full
> > of <VirtualHost ...> tags.
> 
> If you're wary of having that many VirtualHost tags... I'm kind of
> scared to think how many you have. :)

I have about 60 presently and hope to have many more in the nearterm.

Making it a little more friendly to add a new host is the ultimate
goal here.






Mime
View raw message