Does Git, SVN, etc do this type of "branching & merging" or something like this? -
client has different versions of same code based, copy template code base, edit copy, , use copy in production instance of code. meaning there's 20 versions of code base running, 80% of code same. without changing workflow there way merge source code , builds of code if code changes in vcs each of builds/branches. code in perl if matters.
if so, called, , vcs manage "builds" (it's perl, versions of code).
visual: a,b,c custom code branches; x shared code
| | x | /|\ / | \ b c \ | / \|/ | | x | | |\ | \ a,b c | / |/ | | x | | /| / | b,c \ | \| | | etc... x = 80% of code. | |
yes can, before explain it, have recommend not this. better separate variable stuff shared stuff, , turn shared stuff kind of framework, simple moving variable stuff "sites" directory (i'm guessing building canned web sites) 20 subdirectories framework chooses (adds module path) @ runtime (use lib "sites/$site";
might trick, don't quote me on that).
if really, have manage via version control, can create branch each site, maintain core code base on master, , regularly merge master each site in order propagate updates. if variable , shared code cleanly separated, require human intervention.
Comments
Post a Comment