Github's uptime is good enough that I don't see anything inherently awful about a workflow that makes development difficult when Github is down, but any production deployment process that strictly requires anything beyond a working internet connection and a working server to deploy to is insane.
Works pretty well for me. The argument you just made could have - and has - been about any other piece of infrastructure that we now work with third parties for. DNS, EMail, managed hosting, VPS hosting, off-site backups, etc, etc etc. I rely on GitHub to store my code and handle code sharing from separated networks behind NAT - why can't I rely on it for code deployment?
The days of isolating yourself from third parties are over be cause it really doesn't make sense to spend a bunch of man hours setting up and maintaining an infrastructure that GitHub - with the rare exception of tonight - specializes in and has an entire staff dedicated to keeping up and running. Third parties have become mission critical because they save money and time and are generally reliable.
If Travis CI or GitHub stop working I can do a number of things if I really need to deploy - for instance, push to production anyway, which, btw, is also hosted on a third party hosting provider. If several large services start falling like dominoes at once we have bigger problems than just whether my service is running.
Comments
Two third parties, even.
Github's uptime is good enough that I don't see anything inherently awful about a workflow that makes development difficult when Github is down, but any production deployment process that strictly requires anything beyond a working internet connection and a working server to deploy to is insane.
Works pretty well for me. The argument you just made could have - and has - been about any other piece of infrastructure that we now work with third parties for. DNS, EMail, managed hosting, VPS hosting, off-site backups, etc, etc etc. I rely on GitHub to store my code and handle code sharing from separated networks behind NAT - why can't I rely on it for code deployment?
The days of isolating yourself from third parties are over be cause it really doesn't make sense to spend a bunch of man hours setting up and maintaining an infrastructure that GitHub - with the rare exception of tonight - specializes in and has an entire staff dedicated to keeping up and running. Third parties have become mission critical because they save money and time and are generally reliable.
If Travis CI or GitHub stop working I can do a number of things if I really need to deploy - for instance, push to production anyway, which, btw, is also hosted on a third party hosting provider. If several large services start falling like dominoes at once we have bigger problems than just whether my service is running.