Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You missed the most important one:

Have some kind of soaking/testing environment for production critical systems, especially if you're a big business. If you're hip, something like a proper blue/green setup (please chime in with best practices!). If you're legacy, do it all by hand if you must.

Blindly enabling immediate internet-delivered auto-update on production systems will always allow a bad update to cause chaos. It doesn't matter how well you permission things off on your favourite Linux flavor. If an update is to be meaningful, the update can break the software. And clearly you're relying on the software, otherwise you wouldn't be using it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: