Automate Git Repository Setup with Python & Fabric

I love Git.  I find Git to be an intuitive way to track many versions between many systems.  Now all my default config files and scripts utilize Git.  However, logging into a server and creating the Git repo, then cloning it is a number of steps that detracts from getting work done.  

This tutorial outlines a basic example of using Fabric(Python automation module) to automate the process of creating  a ‘mycode.git’ repository and cloning it.  This tutorial was written for Cent OS 6.5, but could be adapted for Ubuntu and Fedora.  Basic knowledge of Linux and Python 3 is required.

If you need help setting up Python3, pip, and Fabric on CentOS 6 please refer to my earlier tutorial: https://www.savelono.com/linux/how-to-install-python-3-and-pip-3-for-centos-6.html

Goals of this post:

  • Write Python/Fabric function to automate the Git setup process
  • Write Python/Fabric function to automate cloning Git repository on local host


Introduction to Fabric

Fabric is a Python library and SSH abstraction layer.  It’s purpose is to easily automate local and remote shell commands as tasks with Python.  Here is a description from www.fabfile.org:


Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks.

It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution

This type of automation is good for me because SSH access is the only common thread for accessing my customers Linux servers.  Fabric excels in situations with many servers located on different networks.  If all my servers were on one network, I’d probably go with Puppet or Chef or some other “state” based system.

Lets start with the Python modules and default Fabric options.  The env.hosts should be set to your Git servers IP address and be configured in a similar manner to my previous tutorial.  Also, notice we created a blank class for handling errors called, “FabricException”.  We will use this later to capture Fabric: aborts, errors, & warnings.

The “env.*” variables are used by fabric to conduct automation tasks.  If left blank you will be prompted by Fabric at execution.



Below is our main Fabric function.  Your fabfile.py can have as many Fabric functions as you want but I tend to divide them up by purpose.  We will alternate between the “local()” and “run()(for remote tasks)” functions of which make up the backbone of Fabric automation.  The function starts by Prompting for a project name, followed by install directory.  It does some basic error checking and then displays your entry.


Now that we have settled on a name we will create the install Git repository in /git.   Remember, in my last tutorial(on installing Git) we created a soft link between /home/git/code and /git(to shorten the string when we connect remotely).


Finally we will create the local directory(if needed) and clone the repo there!

Here is a link to the entire fabfile.py unabridged.

Let’s test it!

[matt@mattcom1 newgit]$ fab newgit
[] Executing task ‘newgit’
Please enter name. Example, ‘myproject’ :mygitproject

Current ~/git/ tree:
[localhost] local: ls -al ~/git
total 48
drwxrwxr-x 9 matt matt 4096 Jun 20 02:58 .
drwx–x—+ 59 matt matt 12288 Jun 20 14:43 ..
drwxrwxr-x 6 matt matt 4096 Jun 20 03:04 fabric
drwxrwxr-x 3 matt matt 4096 Apr 9 22:48 nflrank
drwxrwxr-x 4 matt matt 4096 Dec 30 01:08 puppet
drwxrwxr-x 5 matt matt 4096 Apr 10 14:10 python
drwxrwxr-x 3 matt matt 4096 Jun 20 03:03 savelono-projects
drwxrwxr-x 4 matt matt 4096 Nov 24 2016 swnpc
drwxrwxr-x 4 matt matt 4096 Jun 2 11:42 voiceip

Please enter folder(default ~/git). Example, ‘/home/matt/software’ :

Git Server info
Git Server:
Git User: git
Git Project:

Git Local info
Git Poject name: mygitproject
Git Directory: ~/git/mygitproject

Is this correct? (‘yes’ or ‘no’) :

Type “yes” if the information is as intended.

[] run: mkdir ~/code/mygitproject.git

[] run: git init –bare ~/code/mygitproject.git
[] out: Initialized empty Git repository in /home/git/code/mygitproject.git/
[] out:

Remote Git repo configured!

[localhost] local: mkdir ~/git
mkdir: cannot create directory ‘/home/matt/git’: File exists

Fatal error: local() encountered an error (return code 1) while executing ‘mkdir ~/git’

Directory exist already!

[localhost] local: git clone git@
Cloning into ‘mygitproject’…
git@’s password:
warning: You appear to have cloned an empty repository.
Checking connectivity… done.

Git repo cloned to ~/git/mygitproject!

Disconnecting from… done.
[matt@mattcom1 newgit]$

The directory ~/git exist already, so our exception captured it and the program continued.

our server:

[root@git mygitproject.git]# pwd
[root@git mygitproject.git]# ls
branches config description HEAD hooks info objects refs
[root@git mygitproject.git]#

Our Git client(from which we executed the fabfile.py):

[matt@mattcom1 mygitproject]$ pwd

I’ll create a file ‘savelono.py’, add it as a file Git tracks and push it to the upstream repo.

[matt@mattcom1 mygitproject]$ touch savelono.py
[matt@mattcom1 mygitproject]$ chmod a+x savelono.py
[matt@mattcom1 mygitproject]$ git add .
[matt@mattcom1 mygitproject]$ git commit
[master (root-commit) ea8c083] Add savelono.py
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100755 savelono.py
[matt@mattcom1 mygitproject]$
[matt@mattcom1 mygitproject]$ git push
git@’s password:
Counting objects: 3, done.
Writing objects: 100% (3/3), 218 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To git@
* [new branch] master -> master
[matt@mattcom1 mygitproject]$

That’s it!  Hopefully this comes in use to others that want to automate Git with Python/Fabric.  Thank you for reading.

If you like this article tell Google!!

Written by mattb in: Automation,Linux,Scripts | Tags: , , , , , , ,

No Comments »

RSS feed for comments on this post. TrackBack URL

Leave a comment