On 23/06/10 13:10, Brett Parker wrote:
No it doesn't, it means that you setup the current apache to proxy to the new server whilst migrating the sites. That way you can migrate a site at a time, and then when they're all done, turn off apache and bring the new server up on the correct port.
It did cross my mind that this would be a reasonable option.
One concern I have is that I'll get part-way through the process and it'll stick like that (some sites proxied), because life (other jobs) get in the way. So actually maybe I'm better forgetting about the proxy option and work on the basis that I'll spend a weekend doing the migration then deal with the fallout....
nginx appears to be the current alternative webserver of choice, though.
I'm thinking I should set up a test install and see how I get on. I looked through the config file format and it seems pretty sane.
Of-course the whole discussion is irrelevant unless it is better at separating the virtual hosts - I'll investigate that through their website.