GitHub Firewall Install (your own github)
fi.github.com
fi.github.com
I ordinarily recommend folks not go the installable application route (even though our business is all installable based) if they can avoid it, but I think it definitely makes sense for GitHub. It's an area where the prices are very high, and the products are generally pretty bad.
With luck BitBucket will make a similar move soon - that would be awesome!
One of my startups is thinking about doing something of the sort, for academic institutions to throw our software on their own servers.
GitHub:FI was really built with large customers in mind, places with tens to hundreds of developers bridled with restrictions that prevent them from hosting their code on GitHub.com.
There's no reason smaller companies can't use it, but for the time being we want to dedicate more attention and support to fewer well-paying customers.
We may offer a pricing model in the future that's more affordable for smaller teams, but I can't state emphatically enough that if your team doesn't have the type of restrictions mentioned earlier, you should absolutely be using GitHub.com.
Not using web services has less to do with being bridled corporate restrictions and more to do with preferring to use our nice, fully automated infrastructure. Hosting another small java servlet isn't going to make us break a sweat -- it'll be less work than trying to maintain user accounts and access controls across another web service.
For this reason, we solely use products that drop right into our standing infrastructure. I don't think we're too unusual in this, although we may be amongst the HN sample set.
Although, my initial concern is how this is being spun to customers in terms of customization. One of my design clients is a SaaS vendor that had a large potential customer request an on-site deployment of their big product. Along with packaging up their software for a remote deployment, the customer was asking for all kinds of modifications to match up with their very particular needs. This was sort of spreading them thin on what they could work on for the customer and for the core product. So, my question is are you going to provide customization options for purchasers, or is the product just a rebuilt copy of whatever state the GitHub code is at? I'm a fan of what you guys have built, so I'd hate to see it suffer.
and githubs user centric way of looking at things is much more compelling than the project centric way of gitorious.
“Killer apps makes or breaks any platform. With GitHub, I think the Git hub just scored one.” -DHH
Um. I know DHH is an important guy, but not only is that quote grammatically way out there, I don't think it makes any sense at all...
'Killer apps' make a platform. Lack of 'killer apps' break a platform. GitHub is Git community's (=hub) killer app.
the best I've used so far is trac, but their git support were flaky when I last tested it (only ran well with svn at the time)
I recall it took a bit of finagling to set it up, but I haven't had a single issue with it since. It's also cool that the configuration files are stored in a Git repository (once you try it, it will be clear how that works).
http://scie.nti.st/2007/11/14/hosting-git-repositories-the-e...
I'm using gitosis and redmine internally now, but this one is really interesting