version control - Is there a good strategy to manage multiple clones of a Drupal site? -


i have master copy of drupal site , each client create copy , apply client's branding identity theme , template each site looks different others pretty behave in same way.

now 2 things can happen:

1.a client requests new feature.

if feature other client, merge master copy. if feature useful client, stays clone.

2.a new feature implemented master copy , needs rolled out clones.

overtime each clone has grown differently, how can apply feature clone without interfering existing content , feature in each clone? use feature module it's pain have long every clone enable feature.

it's tricky when come situations drupal settings in file, in database. use drupal 6.x , has been longest lasting pain. svn helps lot in file leave.

has come across strategy?

basically:

  • drupal
    • sites
      • all / modules
      • all / themes
    • site1.com
      • modules
      • themes
    • site2.com
      • modules
      • themes

sites contains modules , themes common through sites (cck, views). sites inherit access them. if need use newer version of cck, put in site1.com / modules, run update.php, , go. if client wants new feature site-specific, write module, drop in site folder. no other site sees it, , site runs code.

for configuration, there features , strongarm let export site features, theoretically drop sites/all/modules , sites have access new feature.


Comments

Popular posts from this blog

apache - Add omitted ? to URLs -

redirect - bbPress Forum - rewrite to wwww.mysite prohibits login -

php - How can I stop spam on my custom forum/blog? -