4 ms·

Indeed, I can't remember a single time where a self-hosted server crashed. They run for decades with 0 downtime.

rvz 5y ago
Exactly. That is the whole point. I keep telling that for GitHub since that goes down once a month. [0][1] GitLab SaSS is the same but a self-hosted backup is better. [0] https://news.ycombinator.com/item?id=29901564 https://news.ycombinator.com/item?id=29901564 [1] https://news.ycombinator.com/item?id=29379648 https://news.ycombinator.com/item?id=29379648
- rovr138 5y ago
  Everyone should have backups and these things aren't infallible. Gitlab is a perfect example. They had database issues and had to restore from backups already.
- miltonlaxer 5y ago
  FYI GitHub Enterprise can be self-hosted https://docs.github.com/en/get-started/learning-about-github/githubs-products#github-enterprise https://docs.github.com/en/get-started/learning-about-github...
sdoering 5y ago
Not sure if this is irony (I often don't identify irony as such). But I fatfingered a lot of self hosted stuff in my time.
- analogsalad 5y ago
  It's full-blown sarcasm. Sorry for omitting the /s.
  - nix23 5y ago
    And i was thinking AHHH he has a old IBM mainframe at home ;)
karmakaze 5y ago
They could, if you stuck to the yak shaving full-time.
- mschuster91 5y ago
  What? Running your own Gitlab instance is one docker command away. No need to shave any yaks.
  - karmakaze 5y ago
    How do you get fault-tolerance, monitor and manage your K8s cluster to avoid service disruptions?
dengolius 5y ago
And even if it goes down you might have more options to get it back to work.
- rovr138 5y ago
  I mean.. you can still use your git repos. Need to do a launch? Build it and push it. Need to share a change with someone so they can review?, `git diff` and send a patch via email. Want to use a server? Spin up a server, add users and keys and push up to it. Gitlab, GitHub and these hosted solutions haven't always existed. They're convenient, but not a OMGWTF moment... unless of course you don't have backups.
oefrha 5y ago
Well, my GitLab instance at some point started to have its Prometheus eat 100% CPU all the time until I disabled the Prometheus component altogether, so there’s that. A cursory glance at the tracker just now says the issue is still open. That’s the kind of problems you get for self-hosting, it’s not all rainbows and unicorns.
- dnsmichi 5y ago
  Hi, Developer Evangelist at GitLab here. Can you link the issue please? :) For context, Prometheus and observability will be handled with Opstrace in the future [0]. I'd like to learn about your use-case and see which troubles you have been running into. Thanks! [0] https://opstrace.com/blog/gitlab https://opstrace.com/blog/gitlab
  - oefrha 5y ago
    This one I guess? https://gitlab.com/gitlab-org/gitlab/-/issues/210365 https://gitlab.com/gitlab-org/gitlab/-/issues/210365 To be clear, I don't care about Prometheus on my instance, I only care when it's causing trouble (e.g. by eating 100% CPU all the time).
    - dnsmichi 5y ago
      Thanks for the URL, and the additional context. Appreciate it. :)
deleted 5y ago
[deleted]
manquer 5y ago
It doesn't, but I can fix it as opposed to waiting for their team to do it. Also at gitlab.com scale the problems they face are very different from a typical deployment. It is like having maintaining your car and using the train. On average if you can fix your car (or hire a good mechanic i.e. consulting) you would probably have a better experience than public transport breaking down, that you are powerless to do anything about. I would rather run a business depending on my car than the train ?
- analogsalad 5y ago
  As a customer of Gitlab, I'm satisfied with their uptime and I have no reason to believe that they can't fix these issues in good time. Yes, I can also fix it if the server was my mine but more than likely I'll be busy doing my actual job (which does not involve fiddling with self-hosted gitlab instances) so I'll take my chances with the Gitlab engineering team. They do fix things and me being busy, asleep, sick, or travelling have no impact on their response. I intend to keep it this way.
  - manquer 5y ago
    Nothing wrong with that outlook, plenty of people do take the train after all extending the analogy further. However ridiculing people who want to their control infrastructure better because they don't have the expertise or time as the guys running the railway gets old.
    - analogsalad 5y ago
      I had no intention of ridiculing anybody, there are things that I self-host but I like to pick and choose my battles instead of a blanket "I must have control over everything" approach. My response was specifically to this comment: > And this is why you self-host on your own instance. This was the commentary on the outage, and it's just outright wrong. Your self-hosted instances will also experience outages. That's the point I inteded to raise.
      - 5y ago

rvz 5y ago

Exactly. That is the whole point. I keep telling that for GitHub since that goes down once a month. [0][1] GitLab SaSS is the same but a self-hosted backup is better. [0] https://news.ycombinator.com/item?id=29901564 https://news.ycombinator.com/item?id=29901564 [1] https://news.ycombinator.com/item?id=29379648 https://news.ycombinator.com/item?id=29379648

rovr138 5y ago
Everyone should have backups and these things aren't infallible. Gitlab is a perfect example. They had database issues and had to restore from backups already.
miltonlaxer 5y ago
FYI GitHub Enterprise can be self-hosted https://docs.github.com/en/get-started/learning-about-github/githubs-products#github-enterprise https://docs.github.com/en/get-started/learning-about-github...

sdoering 5y ago

Not sure if this is irony (I often don't identify irony as such). But I fatfingered a lot of self hosted stuff in my time.

analogsalad 5y ago
It's full-blown sarcasm. Sorry for omitting the /s.
- nix23 5y ago
  And i was thinking AHHH he has a old IBM mainframe at home ;)

karmakaze 5y ago

They could, if you stuck to the yak shaving full-time.

mschuster91 5y ago
What? Running your own Gitlab instance is one docker command away. No need to shave any yaks.
- karmakaze 5y ago
  How do you get fault-tolerance, monitor and manage your K8s cluster to avoid service disruptions?

dengolius 5y ago

And even if it goes down you might have more options to get it back to work.

rovr138 5y ago
I mean.. you can still use your git repos. Need to do a launch? Build it and push it. Need to share a change with someone so they can review?, `git diff` and send a patch via email. Want to use a server? Spin up a server, add users and keys and push up to it. Gitlab, GitHub and these hosted solutions haven't always existed. They're convenient, but not a OMGWTF moment... unless of course you don't have backups.

oefrha 5y ago

Well, my GitLab instance at some point started to have its Prometheus eat 100% CPU all the time until I disabled the Prometheus component altogether, so there’s that. A cursory glance at the tracker just now says the issue is still open. That’s the kind of problems you get for self-hosting, it’s not all rainbows and unicorns.

dnsmichi 5y ago
Hi, Developer Evangelist at GitLab here. Can you link the issue please? :) For context, Prometheus and observability will be handled with Opstrace in the future [0]. I'd like to learn about your use-case and see which troubles you have been running into. Thanks! [0] https://opstrace.com/blog/gitlab https://opstrace.com/blog/gitlab
- oefrha 5y ago
  This one I guess? https://gitlab.com/gitlab-org/gitlab/-/issues/210365 https://gitlab.com/gitlab-org/gitlab/-/issues/210365 To be clear, I don't care about Prometheus on my instance, I only care when it's causing trouble (e.g. by eating 100% CPU all the time).
  - dnsmichi 5y ago
    Thanks for the URL, and the additional context. Appreciate it. :)

deleted 5y ago

[deleted]

manquer 5y ago

It doesn't, but I can fix it as opposed to waiting for their team to do it. Also at gitlab.com scale the problems they face are very different from a typical deployment. It is like having maintaining your car and using the train. On average if you can fix your car (or hire a good mechanic i.e. consulting) you would probably have a better experience than public transport breaking down, that you are powerless to do anything about. I would rather run a business depending on my car than the train ?

analogsalad 5y ago
As a customer of Gitlab, I'm satisfied with their uptime and I have no reason to believe that they can't fix these issues in good time. Yes, I can also fix it if the server was my mine but more than likely I'll be busy doing my actual job (which does not involve fiddling with self-hosted gitlab instances) so I'll take my chances with the Gitlab engineering team. They do fix things and me being busy, asleep, sick, or travelling have no impact on their response. I intend to keep it this way.
- manquer 5y ago
  Nothing wrong with that outlook, plenty of people do take the train after all extending the analogy further. However ridiculing people who want to their control infrastructure better because they don't have the expertise or time as the guys running the railway gets old.
  - analogsalad 5y ago
    I had no intention of ridiculing anybody, there are things that I self-host but I like to pick and choose my battles instead of a blanket "I must have control over everything" approach. My response was specifically to this comment: > And this is why you self-host on your own instance. This was the commentary on the outage, and it's just outright wrong. Your self-hosted instances will also experience outages. That's the point I inteded to raise.
    - 5y ago