News for hackers. Stuff that matters.
Re:Bye Bye Github by vidarh on Monday February 08, 2010 @06:51AM (#1109536)
It is so bad because it fails to take into account that there are multiple failure points involved (his git host, his internet connectivity, multiple transit providers and routers beyond either his or his hosts control, electricity supply etc.) and that getting a more reliable git host won't even address one of them - no hosting will ever achieve 100% uptime, if only because of eventual human error.

He'd be better served first addressing the significant flaw in his overall process of not having a fallback that bypasses as many failure points as possible.

I.e. why does he not have a constantly updated clone of the repositories locally at the provider hosting his actual sites, so that he can deploy as long as he can get hold of an internet connection somehow and is able to connect to his hosting environment?

This bypasses the local electricity supply, his office internet connection, the transit providers between him and Github, etc., because there are many easily accessible ways of getting an ssh connectio in a pinch, and the remaining dependency is his production hosting, without which deployment wouldn't work anyway.

It would be a simple, cheap and prudent safety mechanism if being able to deploy immediately is business critical for him. It's a matter of a single command in a crontab on one or more of his production servers.

There are no comments on this comment yet.