They basically fixed an FTP configuration in Site Studio that was preventing the site owner from publishing on the new server, and reset the quota on both machines. This resolved the two main basic issues preventing migrations. I've had several migrations since then that were totally successful. I know most of the gotchas, which include:
- mail not being migrated properly, requiring manual intervention
- some imports need to be run twice due to path changes in X11
- 32 bit to 64 bit issues in moving PHP sites...including copying libraries and adjusting php.ini
- sometimes some other minor stuff needs to be done
- MySQL quick fix
- will need to modify any oscommerce sites which move from mysql4 to mysql5, usually a "simple" fix, but sometimes nasty with some variants of that software
- need to double check index.html if that's the default page, because on the "double import" sites, it's not always overwriting the default ensim page
Still open is some Site Studio compatibility issues. I hope this doesn't become a big thing. In at least one case, the publishing of the site blew away the left index.
Still to do on the migration that requires special attention:
- move a site with special FTP / user / permissions issues
- move alsonetworks.com
- move support.alsonetworks.com (and upgrade)
- since bashful is a primary DNS this information will have to go somewhere
- at least one client needs to be in on every move
- back up any data NOT in a web site to grumpy somewhere
No comments:
Post a Comment