Comment by nicoburns
8 years ago
I worry about github too. BUT, at least with github most of the data is open. And they have a worthy competitor in Gitlab. Might be a bit of disruption if MS mess things up, but not a disaster.
8 years ago
I worry about github too. BUT, at least with github most of the data is open. And they have a worthy competitor in Gitlab. Might be a bit of disruption if MS mess things up, but not a disaster.
Except for the social part as far as I know, I hope that Bitbucket could see this as a big opportunity and expand that aspect of their platform.
Why not self-hosting?
1. Electricity cost 2. Need for constant electricity 3. Internet cost 4. Need for constant Internet access 5. Cost of hardware 6. Heat generated by the running hardware 7. Noise generated by the running hardware 8. Space occupied by the hardware 9. Need to update and maintain hardware/software 10. Worse discoverability for your repos 11. ISP asking questions 12. Government asking questions 13. Police asking questions
Then again, I live in a "developing" country so most of these might not be an issue for you.
This is a weird comment.
"Self-hosting" doesn't have to mean having a giant server farm at home. You could put it on an AWS/GCP/Azure free-tier VPS instance.
2 replies →
A lot of these would be problems anywhere. Reliability/uptime of electricity/internet is problematic everywhere, although noise/heat I don't see why it would really be much of a problem anywhere.
2 replies →
Most of these aren't an issue if you're self-hosting in the cloud though. You can cheap VPS for a couple of $ a month.
6 replies →
For us (sqlitebrowser.org), self hosting the code, comments, and similar should be achievable with something like Gitea (Open Source GitHub clone).
Hosting our downloads though... hmmm... that could be more tricky.
Our releases generally have ~180k downloads a month, with each being (very) roughly 15MB in size.
That's only 2.5TB/mo, but the downloads aren't evenly spaced throughout the day.
We'd probably need a small cluster of servers with unmetered bandwidth or something. Scaleway might suit.
Its very hard to open issues or PRs etc on many self-hosted setups, as they don't have a way to create logins, or accept other identities.
You can run gogs/gitea and get that basically 'for free'.
1 reply →
If you self-host you will probably never get outside contributions. For most people it isn't worth taking the time to figure out whatever system you use. I'd like to see a federated system like GNUsocial/Mastodon for git. I've thought about trying to make such a system but I don't know much about federation.
I'm not sure what exactly you're reacting to, but a lot of us absolutely do not want to self-host our github repos. Because it's work, because we don't need it, because we like using github/gitlab/other as a "marketplace"
But what about the social / code sharing / collaboration part, which is arguably the most interesting part? We need a quality central meeting place.
People want the nice UI of Github as opposed to just a hosted .git folder, and self-hosting Gitlab is a hassle compared to using a SaaS.