By slashrsm on

Hello,

I am wondering for a best deployment strategy for larger sites. Tracking code changes is pretty easy with some versioning system. But ehat about database?

For example: you have a large site with approx. 100 nodes added every day. At some point you decide to do some further development. At that moment you checkout production files and database to dev server and do the stuff. But which is the best way to merge changes from dev database to production one (which has changed after some time ofcourse).

Is there any common rule for that? How the thing should be done? I found Deploy module, but it is only for version 6 and still in dev stage. Does this module does that job? How about D7?

THX,

JAnez

Comments

slashrsm’s picture

slashrsm commented

Anyone?

--
JAnez

Anonymous’s picture

Anonymous (not verified) commented

I use a mysql mirror where my production server is the master and my dev box is basically a complete slave - rsync works well for mirroring files.

slashrsm’s picture

slashrsm commented

I understand.... But how do you sync changes from slave if you do some development? Shouldn't be changes made just on the master side?

--
JAnez