In my case I have exactly 2 virtual servers, one uses FastCGI and the other
uses HTTP Reverse Proxy so how do I fix this again ?
Also if the new Cherokee fails under a set of circumstances without telling
anyone why it is failing what is the point of this ?
I get what you said and I understand your position but if I do not know how to
resolve the issue of Cherokee suddenly not working then what am I to do about
this ?
Ray C. Horn
CONFIDENTIALITY NOTICE: This email is CONFIDENTIAL and intended only for those
to whom this email has been sent by the original sender. You may
purchase the rights to redistribute this email by clicking here.
> CC: [email protected]; [email protected]
> From: [email protected]
> To: [email protected]
> Subject: Re: [Cherokee] Cannot start Cherokee 0.99.23
> Date: Sat, 29 Aug 2009 19:34:23 +0200
>
> On 29-ago-09, at 19:22, ray horn wrote:
>
> > Why can this not be made part of the installation process ?
> > I mean if Cherokee fails to run unless the required changes are made
> > then why not simply make this automatic ?!?
>
>
> Because, without your intervention, most probably the server wouldn't
> have worked as you expected.
>
> In fact, that'd certainly be a huge issue. I can see it: "Why the
> installation has changed my configuration? Now things don't work as
> before! How dare it modified my configuration? It'd rather prefer to
> do the changes myself. At the end of the day, I'm way smarter with a
> shell script. Does the installation know how I want my server to
> behave? I don't think so!".
>
> The old 'Generic Balancer' is just a subset of the new 'HTTP Reverse
> Proxy'. Thus, there's a number of new configuration parameters you
> ought to check and configure. I don't think auto-configuration was an
> option for this case, actually.
>
> --
> Octality
> http://www.octality.com/
>
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
