Joel Richard writes:
> I thought I'd weigh in on two items of note
>
> On Oct 13, 2009, at 12:17 PM, Scott Gifford wrote:
>
>> When I have done this in the past, I have done it with generating
>> configuration files, so of course one misplaced newline or
>> angle-bracket will kill the server.
On 10/13/2009 12:17 PM, Scott Gifford wrote:
I have had mixed experiences in the past with automatically restarting
Apache after a configuration change. It is very easy to end up with
something unexpected in the configuration, which causes the
configuration to fail, which causes apache to stop.
I thought I'd weigh in on two items of note
On Oct 13, 2009, at 12:17 PM, Scott Gifford wrote:
When I have done this in the past, I have done it with generating
configuration files, so of course one misplaced newline or
angle-bracket will kill the server. Maybe generating the
configuration
"Ryan Yagatich" writes:
> What about mod_vhost_alias? (
> http://httpd.apache.org/docs/2.0/mod/mod_vhost_alias.html )
>
>
> Summary
>
> This module creates dynamically configured virtual hosts, by allowing the IP
> address and/or the Host: header of the HTTP request to be used as part of
> the p
Michael Peters writes:
> Looking at this from a different perspective, have you tried writing a
> monitoring program that looks for updates to the database and then
> would restart the appropriate apache servers on the various
> machines. It would do them one at a time (taking them out of rotatio
Looking at this from a different perspective, have you tried writing a
monitoring program that looks for updates to the database and then would
restart the appropriate apache servers on the various machines. It would
do them one at a time (taking them out of rotation from your load
balancer). I
What about mod_vhost_alias? (
http://httpd.apache.org/docs/2.0/mod/mod_vhost_alias.html )
Summary
This module creates dynamically configured virtual hosts, by allowing the IP
address and/or the Host: header of the HTTP request to be used as part of
the pathname to determine what files to serve.
On Tue, Oct 13, 2009 at 8:08 AM, Scott Gifford
wrote:
>> Sounds like you might be pushing the envelope on what Apache can
>> actually do. If you cannot solve the problem in Apache you could
>> consider relying on Apache default vhost as a way to funnel all
>> requests into a Perl "dynamic vhost"
Thanks William, comments inline...
William T writes:
> On Sun, Oct 11, 2009 at 11:54 AM, Scott Gifford
> wrote:
>> Hello,
>>
>> I'm working on an Apache configuration for a cluster of machines
>> serving a variety of virtual hosts.
>
> I would not try to unify disparate configs into one unless
On Sun, Oct 11, 2009 at 11:54 AM, Scott Gifford
wrote:
> Hello,
>
> I'm working on an Apache configuration for a cluster of machines
> serving a variety of virtual hosts.
I would not try to unify disparate configs into one unless each server
is actually going to service all the virtual hosts your
I don't mean to be a pest but I'd like to further explore using handlers for
Perl sections. Does anyone have any info on this or can point me in another
direction?
I guess I can just put my dynamic configs in a perl module that's not called
as a handler and just 'use' it in the apache config, rig
11 matches
Mail list logo
