5 ms·

This is what I don't get. I trust github as a central platform more than hosting my own gitlab in the cloud. There's a lot of people spreading a holier than th

This is what I don't get. I trust github as a central platform more than hosting my own gitlab in the cloud. There's a lot of people spreading a holier than thou attitude in this thread.

mrsirduke 11y ago
GitHub is a much larger target, and has many, many more moving parts than your average Gitlab on, say, a Linode virtual server. Github will probably have more downtime which you can do noting about, than your selfhosted gitlab, which will probably fail because you upgraded something, or tinkered with a configuration. It's a numbers game. They have more people monitoring, they spend way more money than you do on uptime/services, but such a service doesn't get more stable as it grows. I trust myself way more than I trust GitHub or other hosted/cloud services because I cannot affect/help them in any way when stuff happens. Ultimately, I know this, I accept this, and I happily use GitHub, Bitbucket and such all the time.
- gibsonje 11y ago
  I don't know what to say other than I disagree.
- hn_user2 11y ago
  >Github will probably have more downtime which you can do noting about, than your selfhosted gitlab, which will probably fail because you upgraded something, or tinkered with a configuration. Personally I don't think you will see less downtime on your own server. The difference is, that when it goes down, there is something you can do about it, so you get busy fixing it. When github is down we get to all get online and talk about our woes together. The outages are usually pretty short. Go get a coffee and come back, or grab the team and go play a round of bowling. That has to be better than trying to manage and keep secure our own repos.
  - IE6 11y ago
    This - the last thing I want to do is be on the line when something happens to our git server and no one can work because our solution is my own custom one-off.
nadams 11y ago
Each has it's pros/cons and everyone has their own opinions/needs. For me - github doesn't provide free private repos (exceptions being for class use) and while bitbucket does support free private repos but I believe only a limited number of people can work on a private repo. While I don't collaborate with many people on my ~70 private projects - I also don't want to have to migrate my projects (again - after google code announced shutting down...). Self hosting does allow me to pre-configure repos for use by other people or students. I do self host my repos but I don't use gitlab. The one thing to keep in mind with a service like github - I have seen services that you can run that leverage the github API that fires an event on a new commit to a public repo. Accidentally push your Amazon cloud service keys? Before you even realize it happened - someone will be spinning up VMs or using your S3 service[1]. [1] - http://www.devfactor.net/2014/12/30/2375-amazon-mistake/ http://www.devfactor.net/2014/12/30/2375-amazon-mistake/

This is what I don't get. I trust github as a central platform more than hosting my own gitlab in the cloud. There's a lot of people spreading a holier than thou attitude in this thread.

mrsirduke 11y ago

GitHub is a much larger target, and has many, many more moving parts than your average Gitlab on, say, a Linode virtual server. Github will probably have more downtime which you can do noting about, than your selfhosted gitlab, which will probably fail because you upgraded something, or tinkered with a configuration. It's a numbers game. They have more people monitoring, they spend way more money than you do on uptime/services, but such a service doesn't get more stable as it grows. I trust myself way more than I trust GitHub or other hosted/cloud services because I cannot affect/help them in any way when stuff happens. Ultimately, I know this, I accept this, and I happily use GitHub, Bitbucket and such all the time.

gibsonje 11y ago
I don't know what to say other than I disagree.
hn_user2 11y ago
>Github will probably have more downtime which you can do noting about, than your selfhosted gitlab, which will probably fail because you upgraded something, or tinkered with a configuration. Personally I don't think you will see less downtime on your own server. The difference is, that when it goes down, there is something you can do about it, so you get busy fixing it. When github is down we get to all get online and talk about our woes together. The outages are usually pretty short. Go get a coffee and come back, or grab the team and go play a round of bowling. That has to be better than trying to manage and keep secure our own repos.
- IE6 11y ago
  This - the last thing I want to do is be on the line when something happens to our git server and no one can work because our solution is my own custom one-off.

nadams 11y ago

Each has it's pros/cons and everyone has their own opinions/needs. For me - github doesn't provide free private repos (exceptions being for class use) and while bitbucket does support free private repos but I believe only a limited number of people can work on a private repo. While I don't collaborate with many people on my ~70 private projects - I also don't want to have to migrate my projects (again - after google code announced shutting down...). Self hosting does allow me to pre-configure repos for use by other people or students. I do self host my repos but I don't use gitlab. The one thing to keep in mind with a service like github - I have seen services that you can run that leverage the github API that fires an event on a new commit to a public repo. Accidentally push your Amazon cloud service keys? Before you even realize it happened - someone will be spinning up VMs or using your S3 service[1]. [1] - http://www.devfactor.net/2014/12/30/2375-amazon-mistake/ http://www.devfactor.net/2014/12/30/2375-amazon-mistake/