Lee Daniel Crocker wrote:
The glitch: images. Those are written to the filesystem rather than to the database, so images uploaded on one server will appear in the database of both, but only on one filesystem.
Isn't this true: for all images already uploaded, there is no problem. Only when a new image is uploaded, it will go to one or the other filesystem?
I think this could be tolerable if we disable image uploading on the "old" server (now the "database server"), just to make sure nothing gets uploaded there.
If a few images look broken for 24 hours while DNS propagates, it's no biggie.
Another way to do it is a more traditional switchover that will turn off the scripts on the old server when we enable to new one, and put up a static page that points people to the new server under a name other than "www" while their caches are still live.
That's good, too.
--Jimbo