3 ms·

It depends on your needs and team size. For few tens of dev that need a versioning system with some sugar, a self hosted gitlab can acieve better uptime.

paulddraper 3y ago
> a self hosted gitlab can acieve better uptime. Gonna call BS on that. It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up...
- vb-8448 3y ago
  As I said, it depends on your needs. I don't know if you have ever managed a small gitlab self-hosted installation, but it's really trivial, you set up it the first time, and you forget about it. Also, the upgrade process takes few minutes to complete. Btw, you cannot compare a scheduled maintenance window with an unplanned downtime ... maybe in the middle of an important deployment.
  - paulddraper 3y ago
    > I don't know if you have ever managed a small gitlab self-hosted installation Bitbucket Server
- capableweb 3y ago
  > It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up... Besides the last one, the others you can schedule when developers are not actually working on something, or give a headsup so developers can be prepared in case of errors. In the case of GitHub, Microsoft deploys changes whenever they want, whenever you want it or not.
  - joshmanders 3y ago
    > In the case of GitHub, Microsoft deploys changes whenever they want, whenever you want it or not. That's because GitHub is used by millions of people every day all over the world. Business hours for them are around the clock. No matter when they update, if it breaks something, many people will hear about it regardless of when the break was deployed.
    - capableweb 3y ago
      Yeah, this is exactly my point, their needs don't overlap with your needs, hence sometimes it's better to self-host, because then it's 100% your needs that gets taken care of.
  - RealStickman_ 3y ago
    Good planning and monitoring will also prevent the last point from becoming a problem.
- manojlds 3y ago
  Most of the upgrades happen outside core work hours, which is easy to manage for smaller companies.
- apple4ever 3y ago
  > It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up So 10 minutes a month for upgrades, zero time for the rest because you are managing it just fine.

paulddraper 3y ago

> a self hosted gitlab can acieve better uptime. Gonna call BS on that. It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up...

vb-8448 3y ago
As I said, it depends on your needs. I don't know if you have ever managed a small gitlab self-hosted installation, but it's really trivial, you set up it the first time, and you forget about it. Also, the upgrade process takes few minutes to complete. Btw, you cannot compare a scheduled maintenance window with an unplanned downtime ... maybe in the middle of an important deployment.
- paulddraper 3y ago
  > I don't know if you have ever managed a small gitlab self-hosted installation Bitbucket Server
capableweb 3y ago
> It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up... Besides the last one, the others you can schedule when developers are not actually working on something, or give a headsup so developers can be prepared in case of errors. In the case of GitHub, Microsoft deploys changes whenever they want, whenever you want it or not.
- joshmanders 3y ago
  > In the case of GitHub, Microsoft deploys changes whenever they want, whenever you want it or not. That's because GitHub is used by millions of people every day all over the world. Business hours for them are around the clock. No matter when they update, if it breaks something, many people will hear about it regardless of when the break was deployed.
  - capableweb 3y ago
    Yeah, this is exactly my point, their needs don't overlap with your needs, hence sometimes it's better to self-host, because then it's 100% your needs that gets taken care of.
- RealStickman_ 3y ago
  Good planning and monitoring will also prevent the last point from becoming a problem.
manojlds 3y ago
Most of the upgrades happen outside core work hours, which is easy to manage for smaller companies.
apple4ever 3y ago
> It can achieve better uptime, if you ignore the downtime for upgrades, the downtime for configuration errors, the downtime when the disk fills up So 10 minutes a month for upgrades, zero time for the rest because you are managing it just fine.