4 ms·

Don’t host yourself, it’s impossible to meet the reliability of the professionals

by iso947 6y ago

wizzwizz4 6y ago
No, it's not. Apart from scheduled downtime when nobody's using it (e.g. restarts in the morning to update the kernel), it's not that hard to beat GitHub's uptime for a small Gitea instance. My power's on more than GitHub is up. A UPS and a tethered smartphone would get me three nines uptime-while-anyone-needs-it, which is well in excess of what I need.
- gourmetennui 6y ago
  I think the OP was being sarcastic.
syshum 6y ago
Hmm I am a professional, so it is easily possible for meet my own reliability
bdcravens 6y ago
For many organizations, that's still true.
s_dev 6y ago
... HN is mostly professional software developers though. Running a GitLab instance really isn't hard.
ed1222190 6y ago
I used to agree. Now I work with a locally hosted github. It is down all the time and sometimes it just deletes all of the work from the past day. I thought it wasn't possible to do much worse, but I was obviously wrong.
- js4ever 6y ago
  At work I'm managing a gitlab instance for 15k users and 5k projects. Uptime is 100% since 1 year except for few minutes of planned downtimes every month for the monthly upgrade. To be honest I expected it to be a lot harder and run into troubles ... But I always find answers quickly in gitlab doc or forum
tapoxi 6y ago
We migrated to on-prem GitLab running on k8s via the official Helm chart a year ago. We have ~50 users and so far have only had downtime when they required us to migrate from PostgreSQL 9.6 to 11 with the release of GitLab 13, and that was planned. We upgrade multiple times a month to stay up-to-date with the latest patches, and it's painless. I don't regret it.
subssn21 6y ago
I think that one size fits all host it yourself / don't host it yourself is the wrong approach. For some organizations that have dedicated devops people and can easily maintain their own servers, they may be able to have better uptime and reliability for their instance. For smaller shops that don't have the time or expertise, I think it us true that GIT hosting is one of the many services that should be handled by a Cloud Service whether Github or Gitlab (or someone else).

Don’t host yourself, it’s impossible to meet the reliability of the professionals

by iso947 6y ago

Don’t host yourself, it’s impossible to meet the reliability of the professionals

No, it's not. Apart from scheduled downtime when nobody's using it (e.g. restarts in the morning to update the kernel), it's not that hard to beat GitHub's uptime for a small Gitea instance. My power's on more than GitHub is up. A UPS and a tethered smartphone would get me three nines uptime-while-anyone-needs-it, which is well in excess of what I need.

gourmetennui 6y ago
I think the OP was being sarcastic.

syshum 6y ago

Hmm I am a professional, so it is easily possible for meet my own reliability

bdcravens 6y ago

For many organizations, that's still true.

s_dev 6y ago

... HN is mostly professional software developers though. Running a GitLab instance really isn't hard.

ed1222190 6y ago

I used to agree. Now I work with a locally hosted github. It is down all the time and sometimes it just deletes all of the work from the past day. I thought it wasn't possible to do much worse, but I was obviously wrong.

js4ever 6y ago
At work I'm managing a gitlab instance for 15k users and 5k projects. Uptime is 100% since 1 year except for few minutes of planned downtimes every month for the monthly upgrade. To be honest I expected it to be a lot harder and run into troubles ... But I always find answers quickly in gitlab doc or forum

tapoxi 6y ago

We migrated to on-prem GitLab running on k8s via the official Helm chart a year ago. We have ~50 users and so far have only had downtime when they required us to migrate from PostgreSQL 9.6 to 11 with the release of GitLab 13, and that was planned. We upgrade multiple times a month to stay up-to-date with the latest patches, and it's painless. I don't regret it.

subssn21 6y ago

I think that one size fits all host it yourself / don't host it yourself is the wrong approach. For some organizations that have dedicated devops people and can easily maintain their own servers, they may be able to have better uptime and reliability for their instance. For smaller shops that don't have the time or expertise, I think it us true that GIT hosting is one of the many services that should be handled by a Cloud Service whether Github or Gitlab (or someone else).