I’m working on making it easy to start a centralized Git server with an unlimited number of private Git repositories and unlimited users under your control running on an Amazon EC2 instance. I need people who can help test and provide feedback so I can improve the experience and capabilities.
I’ve used a number of different services to host open source software including Launchpad.net, Google Code, and GitHub. Recently, however, I found the need to host a number of different private repositories and I decided to go with the flow and use Git as the software to manage the repositories.
After investigating a dozen Git private repository hosting options, I decided that they were too limiting for my purposes: number of repositories, number of users, size of the repositories, and/or cost. I also had an urge to keep a bit more control over my own repositories by managing them on my own server.
The commercial Git hosting services are going to be a good choice for many users, especially if you are hosting open source software or need the additional web-based features, but there are some folks like me who may want to run and manage our own private Git repositories.
As I started investigating and building my private Git server, I had to do research to find out what software to use to manage what users had access to repositories and how to configure the server and software. I’ve decided to share the results so far in case this helps others who have similar needs for running centralized Git servers.
The first iteration of the Alestic Git Server is an AMI (available for all architectures in all regions). When you run an instance of this AMI, it includes the basic software required to run a centralized Git server (Ubuntu, Git, gitosis) and you have control over adding new repositories, adding new users, and managing users’ access to the repositories.
Please read more on the project page:
At this point, the project is in its early stages. What is there works for my basic needs, but I’d like to get feedback on things like:
Is it easy to use?
At what point in the documentation do new users get stuck?
What additional features, functionality, software would make sense to add?
Instead of posting comments on the Alestic.com blog, please join the Alestic Git Google group and kick off or join interactive discussions there.
 It has been pointed out to me that running a system on Amazon EC2 isn’t quite “my own server” and that theoretically Amazon has access to my data as much as a Git hosting service would have access to my private repositories. As with any technology project, each individual and company need to make their own judgements about who they trust with what.