Why doesn't GitBucket self-host?
The recent acquisition of GitHub by Microsoft sparked allot of discussions about possible alternatives to GitHub. E.g. one contributor of GitBucket made a topic on Hacker News where users pointed out that not many of these GitHub alternatives are really eating their own dog food.
This might be a valid point, but there are quite a few reasons why GitBucket itself isn’t self-hosted, but still it’s eating it’s own dog food.
The main purpose of GitBucket is to offer an extremely easy to install and use Git Web based UI for small teams and projects, in order to be used in intranets or on private servers for the cases where existing solutions on the market are not an option. GitBucket fulfills this role since years and all the team members and host GitBucket for themselves or in the companies/projects where they work.
Other reasons why GitBucket isn’t self-hosted:
- financial resources: the team is contributing their time and energy as individuals, but for now there’s no company that could finance hosting costs at such a scale on long term.
- ease of contribution by the community – this is the biggest reason.
I guess it’s easier to work at scale on GitHub than on other platforms for our contributors, since they already have GitHub accounts and they are also familiar with GitHub. It motivates the contributors and we can get allot more feedback this way. So using GitHub makes both of us and users happy :) .
I highly respect GitHub because I believe that it changed software development for the better. I always enjoy development on it and GitBucket wouldn’t have been born without it. GitBucket might be an alternative to GitHub, but it’s not a competitor.
Of course, I will keep using GitHub for the GitBucket project in the future too.
Thanks for GitHub as a great software development platform.