Workflow Design - Going from Development to Testing to Production Databases -
i've been trying wrap head around few days now. solutions come little complicated. red flag i'm going in wrong direction.
anyway i'm trying come solid, hands off, work flow going dev prod test server in between.
currently project i'm working on hasn't been launched , not have prod server.
all of developers work locally. changes devs make committed repo , integrated dev environment. have dev server , test server.
the dev , test server databases being handled hand, , launch going problem.
this how propose launch
make copy of test server. copy becomes prod. create master-slave relationship between prod , test data remains consistent. launch site.
every night take data test , give ability refresh database recent data.
developers make changes schema, gets tested, added repo, , goes dev.
the current data , current schema gets merged in dev verify schema doesn't break anything. ready launch new version, bring test.
once changes tested , ready launch make copy of test, (test2) , freeze prod. test becomes prod, prod's master/slaver relationship gets hooked test2, , test2 becomes test.
please don't laugh, best can come with.
any feedback why won't work, or can make better or tools out process great.
Comments
Post a Comment