Managing a drupal installation with cvs and git

Managing multiple drupal installations can be a pain. You have to track changes to drupal-core and all the individual modules that you use, as well as managing your own custom modules and your own custom changes to drupal-core. And if if you’re doing this with several different drupal installations it can get inconvenient quickly.

A lot of this hassle can be reduced by installing drupal from cvs rather than installing one of the releases, and by keeping your installation under version control (in this article I use git but you could use any VCS such as mercurial, svn etc).

Here I describe how I manage my drupal installations using the drupal cvs repository and git.  read more »

» |

A list of interesting Google tech-talks

I’ve watched quite a few Google tech talks in the last few months. There are lots available. Here are some of the ones I found interesting (If you have recommendations for good talks that I haven’t listed below please leave a comment).  read more »

» |

Using git for offline commits to a subversion repository

In my previous post about git I mentioned that one of the nice things about git is it’s support of svn and cvs. I only mentioned it briefly but this is one of the features that keeps making people go “Wow, that’s cool!” when I explain it to them. So you can use git on a project which is centrally stored in svn or cvs or one where other team members are using svn or cvs. Here’s an example of using git with subversion.  read more »

» |

Moving from Subversion to Git for revision control

I’ve been using Subversion for version control for the last couple of years. It’s a lot nicer than cvs and I was quite happy with it. Then last week Olivier pointed me towards a presentation by Linus Torvalds about Git. The talk got me interested in trying out Git and I started playing around with it.  read more »

» |