sanitation@lemmy.radio to Programmer Humor@programming.dev · 7 hours agogithubDownDailylemmy.radioimagemessage-square22fedilinkarrow-up1479arrow-down19
arrow-up1470arrow-down1imagegithubDownDailylemmy.radiosanitation@lemmy.radio to Programmer Humor@programming.dev · 7 hours agomessage-square22fedilink
minus-squareiglou@programming.devlinkfedilinkarrow-up7·edit-22 hours agoNah. If your entire dev team has to be on pause when github is down, you’re doing it wrong. Especially enterprise.
minus-squareEvotech@lemmy.worldlinkfedilinkarrow-up1·37 minutes agoSorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds Off code you could run your own gitlab or whatever but it’s just cheaper and more efficient to buy a sass solution
minus-squareiglou@programming.devlinkfedilinkarrow-up2·31 minutes ago Sorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds You should have both. Having your entire dev team unable to work when one service is down is absurd.
minus-squareEvotech@lemmy.worldlinkfedilinkarrow-up1·29 minutes agoWelcome to the world of SaaS I guess? It’s very standard. I mean GitHub used to have better uptime than you could achieve on your own.
Nah. If your entire dev team has to be on pause when github is down, you’re doing it wrong. Especially enterprise.
Sorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds
Off code you could run your own gitlab or whatever but it’s just cheaper and more efficient to buy a sass solution
You should have both. Having your entire dev team unable to work when one service is down is absurd.
Welcome to the world of SaaS I guess? It’s very standard. I mean GitHub used to have better uptime than you could achieve on your own.