Git on System Overlord

Git On Your Web Server: A Security Reminder

david@systemoverlord.com (David Tomaschik) — Wed, 31 Aug 2011 22:53:21 +0000

Earlier this month, I wrote about managing a Drupal site with git. What I neglected to remember, of course, is this places a full copy of your git repository within your web server's document root. This has the potential to expose any data in your git repository -- a malicious attacker could (depending on your configuration) clone the entire repository, thus exposing source code, configuration files, database dumps, and other sensitive data.

Managing Drupal with Git

david@systemoverlord.com (David Tomaschik) — Thu, 04 Aug 2011 23:40:56 +0000

For a while now, I've been meaning to manage my Drupal site (and the modules and features on it) with git. The release of Drupal 7.7 provided a perfect opportunity to make this transition. I've now cloned the main Drupal.org git repository, added my features (as submodules) and added the modules I use (also as submodules). I'm still getting used to working with git, and I wish there was a way to push parts of my configuration remotely, but I understand why you can't.

Automatically Creating Archives from Git Tags

david@systemoverlord.com (David Tomaschik) — Sat, 16 Jul 2011 13:33:05 +0000

At work, we've been moving all of our development processes to git. As part of that, I've encouraged that alphas, betas, and releases be tagged in git -- it's important to know which versions are in use where. Additionally, my director wanted archives (zips/tars) of each of these versions to make it easier to install the releases, particularly for the members of our department who are not git-friendly. I realized that with git hooks and our use of gitolite, we could produce automated archives when tags with the words alpha/beta/release are pushed to the gitolite server. The script below is placed in the $GL_PACKAGE_HOOKS/common directory. It uses the name of the repository to decide if it should be archived (matches $ALLOW_ARCHIVE) and where the archive should be put (within $ARCHIVE_DIR).