Request a live demoof the Acquia platform
Is version tracking Drupal core or things in contrib that you tend
not to hack really a best practice?
In <a href="http://
hawidu.com/2011/12/09/drupal-and-git/">a presentation to
DrupalCamp Michigan about git</a>, I tried to make the case that
your version control environment should be reusable units; a custom
module for one site might be appropriate for a later site, for
instance. Things like core and contrib, unless they're necessary
to edit, can best be controlled, deployed, and upgraded when left to
their own devices.
There's an appeal to organizing site files as a cohesive
whole. I just wonder whether this strategy is more manageable than a
More information about text formats