When it comes to the strategies surrounding updates of a Drupal site there are many options to choose from; some are heavy duty, like pushing changes using Chef or Puppet and some less so, like manually logging necessary changes. But there are also strategies that lie in between these extremes.
We all know that the git command is a veritable swiss army knife of development goodies. So it should not come as a surprise that git itself can be used to manage deployments and updates. In fact, git is used internally by the likes of OpenShift and Heroku to manage the deployments of their services.
In this session I will walk you through setting up a git server that deploys changes via a git post-update hook script. Such servers are an easy way to get into continous integration without having to learn any new DSLs, and the technique can be applied to any project not just a Drupal project, whether it's hosted on your own servers or on the likes of GoDaddy or an AWS instance (etc.).
A repository related to this presentation is available for forking on Github (https://github.com/dkinzer/dkicker).
A link to better credits: https://gist.github.com/dkinzer/53816d501bd531aba586