Easy Fabric Deployment, Part 1: Git/Mercurial and SSH
September 22, 2009 | code, django | 3 comments
We’re firm believers in the practices described by the Continuous Integration method of software engineering. Among those are:
- Maintain a code repository
- Automate the build
- Automate deployment
We use git for our code repositories and Fabric to automate our build/deployment process. The tiny bit of overhead it take to write out a Fabric script pays off very quickly against the tedium and error-prone practice of manually building/deploying. In building our “fabfile”, we encountered a couple of issues that took a little head-scratching to work out.
Git and SSH Keys
Git, like Mercurial and others, confirms your credentials via an private/public key pair when used over SSH. We use gitosis to manage our private repositories, so managing everyone’s keys isn’t much of an issue. The problem comes when developers need to start pulling the repository on different machines. Our developers all push to a central ...

