News for hackers. Stuff that matters.
Re:Incident with GitHub Actions and Codespaces by dx034 on Thursday April 14, 2022 @04:39AM (#31024586)
We don't have an overly complex setup, just some automations along the way to make things easier the long way. Sure, it's a bit more complicated than manually installing a server, but learning how to use terraform and automating patching/backups etc isn't rocket science.

Anyone with some knowledge of Linux/Programming shouldn't struggle setting this up within a few days. And it adds knowledge to the company that's very valuable.

With Gitlab, as with most software, restarting it regularly outside of office hours is the best way to ensure a stable service. Also something SaaS can't do, as they never know when their customers need the software.

Re:Incident with GitHub Actions and Codespaces by thih9 on Thursday April 14, 2022 @04:51AM (#31024633)
Many companies with on prem setup also don’t know when their devs need the software. Some have people in multiple timezones, some do async work, etc.
Re:Incident with GitHub Actions and Codespaces by vorpalhex on Thursday April 14, 2022 @09:49AM (#31026956)
Yeah but how bad is a 5 min restart for that one dude in Australia at odd hours?
Re:Incident with GitHub Actions and Codespaces by thih9 on Thursday April 21, 2022 @04:56PM (#31115076)
How bad is a github downtime? I guess it all depends.