Skip to main content

Gitblit: Stories from the Field

Continuing my little tribute to the Gitblit 1.0 release, I asked some old colleagues of mine, Leif and Trygve, about their experiences with using Gitblit in practice.

Q: How do you use Gitblit?  

Leif:
Webstep is a consultancy company, and we needed a Git repository for a specific client project that is being run in-house.

At the moment the Gitblit server hosts three different projects, but only one is in active development.

Trygve:
I was working as a consultant in a team that was currently using Subversion, but wanted to switch to Git. IT were working on an installation of Gitorious, but the project didn't have a very high priority.

As an intermediate solution I looked around for small, simple solutions for hosting a low number of repositories (around 10). As it was only our team that was going to use it, we didn't have any need for complicated security setups, just plain hosting. Having a web interface was a big plus as I wanted to show it was easy to create lots of small projects, instead of those big lumps we ended up with in Subversion. The team was also going to split their one big web app into two smaller apps.

We use Gitblit as a central Git server for our team. Later on other teams that wanted to try out Git started to use it as well.


Q: Any other products you were considering? Why did you pick Gitblit over them?

Leif:
Our server infrastructure is Microsoft based,  and we needed a solution that was easy to install and maintain.  

Keeping costs low is important to us and our clients, so a for-pay solution was really never in the picture.

Off-site hosting like Github, Bitbucket and Assembla is problematic for most client projects in a number of ways, so that was really not an option either.

I had a look at the managed server and local install option of Gitorious, but they were too expensive for our simple needs.

So I tried a "manual" install of a barebones Git server, but found it non-trivial on the Windows server.  Gitblit took care of that in a matter of minutes, and I haven't looked back ever since.  

Trygve:
- Gitorious (too complicated to set up)
- Just use an account at Github - not allowed by IT
- Custom scripts + gitweb - too much work, at least when Gitblit was so easy


Q: Anything you particularly like or dislike about Gitblit?

Leif:
I like the simplicity of it.  The webpage is nice and clean.  Functionality is sufficient for our needs.
At the moment we are just two developers rebasing off each other, so we do not need more advanced functionality like pull requests.  

When I first installed Gitblit Go, the windows service would die immediately after starting up. It turned out that one needs the 32-bit version, even if the server OS is 64 bit. Thats the only problem we've had so far.

Trygve:
Ease of use, definitely. Just click click and you're done. Sending links to diffs and stuff is also very useful. Having the dashboard to show an overview over what's happening is nice.

No dislikes in particular. I didn't try the advanced features, but as a small Git server, it's the shit.

I had to implement security integration with Crowd but that was easy enough. Took about 3-4 hours from start to end.



Q: Any final notes or comments about Gitblit you want to share?

Leif:
Gitblit has served us nicely so far, and I won't hesitate to recommend it if you need a no-fuss Windows-based Git server.


Big thanks to Trygve and Leif for doing the interviews!

Comments

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

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

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

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 --