Yes John, I would prefer never to stick with that prod too, indeed I have to. It's a business requirement in this case. The future contract depends on what the performance will be achieved on that sever. The customer does not care too much about the demo (made) on dev. They wish to measure the performance on prod exactly, using the real data. And, the customer is right (as always;-)...
Thanks, Slava ----- Original Message ----- From: "John D Groenveld" <[EMAIL PROTECTED]> To: "Slava Bizyayev" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, April 06, 2002 3:10 PM Subject: Re: sun4-solaris polluted installation > If you're doing a demo, then I'd advise against installing over > the production distributions. > > Create your own perl and Apache's. > > Philippe Chiasson wrote a paper for either ApacheCon or PerlCon about > managing multiple modperl developers. If I recall correctly, each developer > had their own Perl and Apache's living in each user's home directory > with a CVS checkout of the latest application code. Before they were rolled > out in production, he could then test against his copy of the current > production environment. > John > [EMAIL PROTECTED] > >
