Search This Blog

Gitblit - The Little Git Repo Manager That Could

Seeing Gitblit v1.0.0 was released a few hours ago (Google+), I would like to celebrate and congratulate the project with a two blog-posts. This is the first, and the second I hope to do soon in shape of some interviews with a couple of Gitblit users.

Uh, what is a Git repository manager?

It can be several things. Most people look for these features in a repo manager:

A central place to share repositories

A web-frontend for said repositories

Manages users and access-control

Just to mention an alternative setup: At my dayjob, we use:

A simple folder on a Linux server to put central repositories, accessible over SSH

We're quite happy with the above setup because we are a very Linux/Mac oriented shop, with a small team that have no fancy requirements on the access-control part. For a larger, Windows based shop it won't be so easy.

An alternative is to use Github, which is probably the best all-round solution for repository management. But it costs money, which can be a hard pill to swallow for some organizations.

Other free alternatives are Gitorious, Gitlab (wich uses Gitolite) and Gitolite, but I think these three are pretty Linux oriented.

Note that both Gitorious and Github are available in SaaS form (that is, you store the central repositories on their servers, so you don't need any infrastructure yourself), and they are free to use for open-source projects.

My favorite things about Gitblit

It's Java. Call it a plus or a minus, but a cool consequence of this is that Gitblit has Groovy hooks.

Another consequence: Runs well on Windows.

Great just-works factor

Wait, who makes this Gitblit anyway? What's the catch?

No catch, it's just a project that was started to scratch an itch. It's a really charming story really. James Moger, the author of the project, wrote about it a while ago, and I recommend you give it a read.

A small tour of Gitblit

I just took version 1.0.0 for a spin on my Ubuntu laptop. Downloaded the Gitblit GO, unzipped and started with java -jar gitblit.jar (could it be any easier?).

Just started Gitblit GO, no configuration necessary

Browse to https://localhost:8443/ and there it is (it generates a self-signed https certificate if you don't tell it otherwise, that's why you get a warning in your browser).

First view of Gitblit. You'll need to log in as admin/admin top-left there to start creating repos

Just created an empty repo. Note the helpful instructions for getting started.

Note that I had to do:

git config http.sslVerify false

in my local repository before I could push as described above (more about this in the Gitblit Setup docs).

Labels

Popular posts from this blog

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git -> ~/.atom/*

config-mr.git -> ~/.mrconfig -> ~/.config/mr/*

config-tmuxinator.git -> ~/.tmuxinator/*

config-vim.git -> ~/.vimrc -> ~/.vim/*

config-bin.git -> ~/bin/*

config-git.git -> ~/.gitconfig

config-tmux.git -> ~/.tmux.conf

config-zsh.git -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

Disclaimer: I do not recommend using earphones while on your bike, but there are times or roads where I think it's OK. Pull out your earphones when nearing potentially dangerous situations (like intersections). At least pause the audio.
These tips also apply to anyone unable to look at and touch their device, leaving voice commands their only option (useful for visually impaired people, people wearing thick gloves, etc).
First of all, you need an Android with a fairly new version of Google Now installed, like Lollipop. You'll need a headset with a microphone button. I’ve got an iphone headset that works great with my old Moto G, excluding the volume control.
You need to make sure that a connected headset can bypass the device’s lock mechanism. It’s in:
Settings -> Language & input -> Google voice typing -> Hands-free
Your audio playback software has to work with the Google Now commands. I’ve tried Google Music and BeyondPod successfully.
So, off we go! You’…

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…