Thread

I am currently working on a site which is being developed on a local EE install, and shortly after developing another site for them.

But I will be deploying the site onto the clients server which already has an EE install, so if I purchase MSM, how do I go about merging my existing EE database with the local install I am using to create the second site..

When I deploy a site, I generally do a remotely connect to my EE database and upload from the local mamp server.

But this would obviously overwrite the existing sites content.

And if I purchase MSM for EE2 will this include the MSM files for 1.6.8?

Cheers
Lee

Hi, Lee,

There is no out of the box way to merge two separate installations into an MSM installation.  You would need to create that solution or move items manually.

Yes, MSM2 will include the 1.6.8 files in the download package.

Thanks Lisa -

So what do you think the best plan of attack would be to manually move it?

Should I start using MSM now on this local build of the new site which is running as a subdomain.
Create a new local subdomain for the site which is already live and manually add that site to my local build.
Then redeploy both sites to the live server?

I am guessing all the individual sites data is contained within the same db tables, so when it comes time to building the third site would be best done on a passworded domain on the live server?

Whats the actual difference in the database for each site?
Are the sites tables prefixed uniquely or does each entry have a site id column?

Manually moving it means manually copying over the templates and entries into the new Site.

The easiest path is to start in the MSM and build it out there.  You can keep that Site offline while you build it, or password protect the whole folder.

There are site_id columns.