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.
Labels:

Comments

  1. Unknown18/12/12 06:31

    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. tfnico18/12/12 07:14

    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...
6 comments
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

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 --...
12 comments
Read more