Skip to main content

Gitblit - The Little Git Repo Manager That Could

I've been tweeting about Gitblit every now and then, and also recommended it to people who want to run some Git infrastructure on Windows.

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
  • Gitweb as a web-frontend
  • Access-control with SSH users and certificates
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 free/open source (Apache license).
  • Comes with authorization built in. No need to figure out OpenSSH on Windows (a lot of people really struggle with this).
  • 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).

First repo up and running!
Managing users and teams in Gitblit

Pretty, isn't it? It also runs well on Windows of course, also as a Windows service (with the right coctail of Java versions and configuration).

There are more screenshots on the Gitblit homepage, and also a live instance you can try out.

I'll come back to some more reasons on when or why you should choose to run Gitblit in the next blog post.

Comments

  1. hello, your information is very interesting but I would like you to talk a little about federation, I have a question I can create a copy of a repository for security and to leave actomaticamente updating?

    ReplyDelete
  2. Hi Diana, thanks for commenting. You'd better take up questions like that on the Gitblit mailing list.

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Encrypting and Decrypting with Spring

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

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --