In switching web servers I thought it would be straightforward to copy over the code from the current location, update the mt-config and presto, site back online. =)
Where I'm having trouble is the site path for each individual blog. The absolute path from the original location is not the same as the path in it's new location and I'm using the same database server as the original server. So two web servers and a single database. Is there a way to set the site root for each blog to a relative path from the web root. I see it says "you can also use a path relative to the Movable Type directory." in the settings, however, we can't display static files in the cgi-bin so the actual site root is a level up from cgi-bin...
.../public_html/cgi-bin/mt/ #Movable Type home
.../public_html/blog/ #Site root published files
.../public_html/mt-static/ #MT Static files
I've tried a couple different things to no avail. Any insight would be awesome.
Reported on Movable Type 4.3
Why two servers and a single database?
Clone everything on the new server, then update the database from the new server to use the new server paths for each blog and you are done.
Then switch the domain DNS to point to the new server and you will be up and running from it, within up to 48 hours, time needed for the DNS propagation all over the web.
Kind Regards,
Mihai Bocsaru
----------------------------------
Daily Movable Type Consultant
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
----------------------------------
Open Melody Demo
http://www.openmelodydemo.org/
48 hours of downtime is a ton. Granted it usually doesn't take that long. The thought was to make the switch seamlessly with no downtime and no need to merge changes from the original database.
Did I mention a downtime? No, I don't think I did :)
And if I didn't, it means there is no down time.
You could hold on publishing and close comments before the moment when you start cloning, and then reactivate the comments on the new server.
As for posting, you could post on both places if you cannot hold from publishing new stuff for those up to 48 hours...
=D I see what you mean.
So start up a new database on the new server, clone the original db and then only update the settings on the new install. Then the site is available on either server depending on how fresh the DNS is. Disabling comments shouldn't be a problem and making the DNS switch over the weekend should keep posting to a bare minimum.
Definitely a possibility... I'll have to see what is involved in duplicating the DB. It's not a typical MySQL setup.
Yes, that is what I am saying and I am also available for consultancy if you want me to do this on your behalf.