Re: [Phplib-users] phplib 6.1, php3 and php4

[Andrew C. <An...@Ev...>]

FWIW: With the low cost of hardware and the high cost of pissing off 
customers these days, the best way to do this is to (1) set up the new 
configuration you want on a new server, (2) install the customer sites, one 
at a time, on the new server, (3) resolving any problems you discover, one 
at a time, then (4) make the new server live (either by changing DNS 
records (preferred) or by decommissioning the old server and re-assigning 
its IP address to the new one (less preferred.))  That way, you have much 
less potential for interruption in service and can immediately revert to 
the previous configuration in the event of disaster.

If you have two servers with identical hardware, you can "leapfrog" them: 
proceed as described above, when you are ready to do the next upgrade, 
re-install the older one with the new configuration and repeat.  During 
normal operations, you can use the unused server as a redundant failover - 
i.e. configure it just like the live server and mirror data to it.  If 
something bad happens to the first server, make the other one live.

Andrew Crawford
An...@Ev...

At 02:52 PM 1/22/2002 -0600, you wrote:
>Thus spake Layne Weathers on Tue, Jan 22, 2002 at 02:41:31PM CST
> > > the version of phplib that is in testing and stable is very
> > > out of date.
> > > The version that stable is using was never released and
> > > shouldn't be on
> > > a production server.
> > > grab the version of phplib from unstable, is it actually the
> > > most stable
> > > version.
> > > http://packages.debian.org/unstable/web/phplib.html
> > >
> > >
> > > At this point testing is more stable than stable for
> > > apache/php4/phplib/mysql etc
> >
> >
> > No, no, no. Why would you rely on a package created by a Linux distribution
> > company? There is no way that they can keep up to date on all the little
> > projects they include on their disks and if they are building their package
> > from the latest releases instead of the CVS tree then you are really out of
> > luck.
>
>Actually, I installed phplib from a tar package from the author's website.
>When I installed it, v 6.1 was the newest version.  All my customer's
>websites are built against phplib 6.1.
>
>I would very much like to upgrade the whole she-bang.  The issue, which
>everyone seems to have missed, is that this is a _production server_.  I
>host sites which my customers are paying me to keep online rock-solid and
>unbroken.  If I intend to upgrade to php4, I need to know _very
>specifically_ what I can expect to break in existing code so that can either
>preempt any problems or fix them quickly if I get complaints that something
>on someone's site has stopped working.
>
>--
>Lindsay Haisley       | "Everything works    |     PGP public key
>FMP Computer Services |       if you let it" |      available at
>512-259-1190          |    (The Roadie)      | <http://www.fmp.com/pubkeys>
>http://www.fmp.com    |                      |
>
>_______________________________________________
>Phplib-users mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phplib-users