Updating hosts file is super easy! Any sed, echo, vim command will work.
You’re perfectly safe, if all changes only come from the automation. And your code is bug-free.
But in the reality, you might have surprises. Especially when people might change it manually.
My Suggestion? Before making any changes, confirm all customizations are expected. If not, abort the changes with proper alerting.
Don’t make manual changes to the hosts file in your servers.
It would be hard to maintain. If you have to, here are 5 common issues I’d like you to know. And also some tips and free tools included in this post.
Check it out! And share it with your friends, if you find it useful.
When you hand over developers new VM(s), or when you have just created a critical env for your team, remember to be prepared for low disk issues.
If you don’t, it will bite you sooner or later. More annoying, it usually come out as a recurring issue. Evaluating the total support effort, we might get a much bigger number than we thought. Are you feeling the same, my friend?
So how we can make low disk issues less likely to happen? And when it does happen, how we can resolve it faster with less impact?
The more projects you handle, the more servers you manage. But when you ssh to servers of different projects, are you using the same private key?
And how secured you feel about this? Let’s imagine. One day, your powerful private key gets compromised somehow. Boom! All your servers, and all your projects are in danger.
Check out this post. And get improved for all your projects, in just five minutes!
Say you have issued a command in your servers. Typically the command might either backup something or perform a critical hot fix.
Surely you know the start time of the process. But when it will end? How can you find the execution time, when the process has already been started?