6 ms·

I was working on a project which uses github.com. I never knew before how often github is actually down. A business is often enough to spend that extra cash to

• jjeaff 8y ago
  As is the risk of not being able deploy because your self hosted service is down.
  • miguelmota 8y ago
    Touché, although the main difference is that you have full control and transparency in the self-hosted system and you're not at the mercy of the third party's slow hotfix release process
    • mdekkers 8y ago
      Exactly. Also, very likely for self-hosted to have a lot less moving parts, so less likely to go down
  • rhizome 8y ago
    self-hosted git isn't going to go down in the complicated ways that running it for zillions of people does. a lot of things are relatively set-it-and-forget-it on the server side at the scale of most companies (let's BS it as <200ppl).
    • asdkhadsj 8y ago
      Yea, I feel like the "going down" metric is completely different. With Github, it's very possible that their seemingly frequent outages will cause problems for your deploys/etc. Yet, those problems will likely be short lived. On the flipside, your tiny instance of Git will likely be more stable than Github, but if it does go down you better hope you had proper backups, can spin those backups easily, etc. It might be down for days. It's unlikely to happen, but you can't just go get coffee. Though, with the right self hosted solution, it should be fairly trivial to deploy a new instance, restoring from backup/etc. The concern would be data loss, but even at that, it's Git so you're likely fine due to distributed backups.
      • WrtCdEvrydy 8y ago
        This is what I'd love to see, a local git-like instance to syncs to Github.
        • jsjohnst 8y ago
          Put this in a cronjob: git remote add github url_to_repo git push —mirror github
          • fiddlerwoaroof 8y ago
            This is what post_receive hooks are for.
            • jsjohnst 8y ago
              Depends on what you’re using for the local Git server. Sometimes it’s not easily doable, but yes, if possible using hooks is better.
        • fiddlerwoaroof 8y ago
          gitolite + gitolite-simple-mirror is amazing for this.
  • geezerjay 8y ago
    > not being able deploy because your self hosted service is down. If you're using git then you already have the whole repository everywhere you've cloned the remote repository. Therefore, your example is at best implausible.
    • fs111 8y ago
      People rely on things like Travis that are tightly integrated with github. Even if you have a full local checkout, you probably cannot deploy easily, if at all. Not saying this is good, just a fact these days.
      • geezerjay 8y ago
        > People rely on things like Travis that are tightly integrated with github. That's a github-specific problem, not a git-specific problem. It doesn't make any sense to assume that a github-specific workflow would apply to a scenario involving self-hosting a git repository.
  • mbrumlow 8y ago
    But at least if my self hosted service down I know the solution is in my hands. And I can give reasonable expectations when it will be back up. This in my opening is far better than looking at a red Dot on a status page. Man have we lost some real know how and decided big sevises are the "way to go". It's not if your service -- self hosted or not -- it's when your service goes down. I run both a gogs server and depend on GitHub. In the last 3 years GitHub has been down for my repos at least 2 times. My gogs instance has had zero down time ( minus breif upgrades ). We really need to start checking out self on the dependency of 3 party service. There is no guarantee they will be available forever or that they will work the same 10 years from now. And if your build system depends on any of these services good luck with useful code eacrow.
    • mbrumlow 8y ago
      I really need to stop trying to type replies while holding a screaming baby in one hand.... Oh the typos! 1) self hosted service goes down 2) opinion 3) dot 4) start checking our selves There are more I am sure, but I have no more time, back to holding a baby. Also, stupid phones without physical buttons don't help.