3 ms·
I don't understand the panic. This isn't a black-box system, it's github. Owning your artifacts is as simple as setting up a job to automatically clone the rep
by brundolf 5y ago
I don't understand the panic.
This isn't a black-box system, it's github. Owning your artifacts is as simple as setting up a job to automatically clone the repo a couple times a day (assuming your entire company is working through the cloud interface and not a single person already has a local checkout).
Lots of companies put their entire databases in AWS - owned by a company that's already evil, no speculation required - where the egress charges make offsite backups a challenge. And western civilization hasn't collapsed yet.
If GitHub changes its policies one day or shuts down the service... just push to a new repo and switch over to regular workstations.
- remexre 5y ago> This isn't a black-box system, it's github. Owning your artifacts is as simple as setting up a job to automatically clone the repo a couple times a day (assuming your entire company is working through the cloud interface and not a single person already has a local checkout). Isn't the use-case they're selling in the article approximately "the development environment setup is so fragile that it doesn't work on lots of machines?" I'd be willing to wager that after a few years of the whole team using this, the fragility will be much worse, so moving away will be that much harder.
- brundolf 5y agoFragile in the sense that it might take you hours or days to get it all set up just right. It would be a disruption, like any IT problem, but it's not going to threaten an entire business.
- vbezhenar 5y agoI might be wrong, but it seems to be a combination of visual studio code + container plugin + docker. So you would need to install visual studio code, few plugins and spin up a docker to replicate that environment on the local machine.