Charles Bailey takes a look at Git Index’s internals, explaining why it is used, what and how is stored in it, and what operations can be used against it.
Justin Beckwith introduces several ways to deploy ASP.NET, Node, and PHP applications to Windows Azure, including git deployment, TFS deployment, continuous integration and custom scripts.
Johan Herland explains how Git does branching and merging in a distributed (and partially disconnected) environment, how to rewrite a commit history, and why staging is useful.
Ian Goodsell discusses the challenges encountered with tool versioning and new approaches needed to support continuous delivery.
Ignaz Wanders discusses service versioning, compatibility issues, and how to implement the governing process of service versioning.
Jesse Newland discusses how GitHub pages were re-written with Erlang, Riak and Webmachine in order to improve their performance.
Zach Holman shares insights on creating a happy experience fueling developers’ creativity, being inspired by how things are done at GitHub.
Ryan Slobojan discusses how to perform issue tracking, code review, commits and builds in an automated manner by integrating Git, Gerrit, Hudson and Mylyn.
Ryan Slobojan presents Code2Cloud used to automatically set up a number of tools useful for development and deployment: Hudson, Git, task repository, wiki, Cloud Foundry Deployment Services and Maven.
Scott Chacon explains the internal mechanisms used by Git to do version control based on three trees –head, index, work–, and some of its commands, especially ‘reset’.
Greg Young discusses how to use events to store data, and how testing, versioning and performance are impacted by an event-centered model.
Joe Williams discusses how distributed systems, cloud computing and configuration management affect system’s availability. He exemplifies with a database service built on CouchDB, Erlang, Chef, EC2.