3 ms·

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 invol

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?

creshal 6y ago
Git is decentralized by default, so all you really need is for your self-hosted version to not crash at the same time as github does. That's not too hard to pull off.
gregoriol 6y ago
It's not that I'm against, the contrary, but in the last months I've experienced a physical server crash, a random kernel panic and a failed upgrade of GitLab: that all took 10/20 hours of work, didn't result in any data loss, but the downtime was clearly higher than what GitHub has (+ nobody on the team was on holidays at that moment), plus any maintenance like software or system upgrades has to be done outside team working hours to limit the impact.. real self-hosting is not that easy!
- ashildr 6y ago
  A failed upgrade of GitLab? Can you give details - I got used to monthly Gitlab updates going very smoothly and now I’m a little afraid. What went wrong?
  - gregoriol 6y ago
    Last one we had was because the ssh connection was lost during the apt upgrade (gitlab omnibus ce). Another one I remember was when some new configuration key was needed and prevented one of the components from starting (took ~2 hours to find what it was). It doesn't happen often, don't worry that much though, gitlab omnibus works well, but is hard to investigate/fix because it's huge and not a tech stack we do understand well since we mostly use gitlab-ctl commands, so when something goes wrong it's hard
aabbcc1241 6y ago
If you just need the standard git functions, you just need an low-end linux machine with ssh server to "self host git"
HelloNurse 6y ago
No random high-risk infrastructure updates? A server is more likely to go belly-up by accident than the presumably redundant GitHub infrastructure, but its life is much less interesting.
koonsolo 6y ago
This is an issue I see at a lot of companies make, even going further than self-hosting. For example replacing off the shelf software with an internal product. "This is not good, we have to do this ourselves". And in the end it costs way more, and you end up with an inferiour solution because it's not your core business, and nobody really has any time to work on it. Very sad really. The first thing to ask is exactly what you asked here. I can't upvote this enough.

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?

creshal 6y ago

Git is decentralized by default, so all you really need is for your self-hosted version to not crash at the same time as github does. That's not too hard to pull off.

gregoriol 6y ago

It's not that I'm against, the contrary, but in the last months I've experienced a physical server crash, a random kernel panic and a failed upgrade of GitLab: that all took 10/20 hours of work, didn't result in any data loss, but the downtime was clearly higher than what GitHub has (+ nobody on the team was on holidays at that moment), plus any maintenance like software or system upgrades has to be done outside team working hours to limit the impact.. real self-hosting is not that easy!

ashildr 6y ago
A failed upgrade of GitLab? Can you give details - I got used to monthly Gitlab updates going very smoothly and now I’m a little afraid. What went wrong?
- gregoriol 6y ago
  Last one we had was because the ssh connection was lost during the apt upgrade (gitlab omnibus ce). Another one I remember was when some new configuration key was needed and prevented one of the components from starting (took ~2 hours to find what it was). It doesn't happen often, don't worry that much though, gitlab omnibus works well, but is hard to investigate/fix because it's huge and not a tech stack we do understand well since we mostly use gitlab-ctl commands, so when something goes wrong it's hard

aabbcc1241 6y ago

If you just need the standard git functions, you just need an low-end linux machine with ssh server to "self host git"

HelloNurse 6y ago

No random high-risk infrastructure updates? A server is more likely to go belly-up by accident than the presumably redundant GitHub infrastructure, but its life is much less interesting.

koonsolo 6y ago

This is an issue I see at a lot of companies make, even going further than self-hosting. For example replacing off the shelf software with an internal product. "This is not good, we have to do this ourselves". And in the end it costs way more, and you end up with an inferiour solution because it's not your core business, and nobody really has any time to work on it. Very sad really. The first thing to ask is exactly what you asked here. I can't upvote this enough.