(Replying to PARENT post)
Could you provide details on how you plan to be more reliable with a self-hosted solution? what kind of archtecture would you use? how many people will be involved in maintaining?
๐คgregoriol๐5y๐ผ0๐จ๏ธ0
(Replying to PARENT post)
I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?
๐คdt3ft๐5y๐ผ0๐จ๏ธ0
(Replying to PARENT post)
Self hosting GitHub is an option as well. We've been self hosting GitHub Enterprise for years and it has had no downtime other than during scheduled updates (at night, when nobody's at work).
๐คtrulyrandom๐5y๐ผ0๐จ๏ธ0
(Replying to PARENT post)
self-hosting requires quite a bit of scale to be more reliable, otherwise you'll most likely still have possibly longer outages, just at different times.
๐คdtech๐5y๐ผ0๐จ๏ธ0
(Replying to PARENT post)
You can self-host GitHub too. Or BitBucket.
๐คrplnt๐5y๐ผ0๐จ๏ธ0
(Replying to PARENT post)
Another reminder to self host via solutions like GitLab or Gitea. [1]
[0] https://news.ycombinator.com/item?id=23675864
[1] https://news.ycombinator.com/item?id=23676072