Configuration Management Tools

You might want to start using a proper configuration management tool like Ansibe,Chef,Puppet, or Salt

Much better option: puppet, chef, ansible, or any other configuration management / automated systems administration tool.Stop logging in to boxes to change them. Instead, make a change in your version-controlled config repository, get a machine to test it, and if it works, roll it out to all the machines with that role. Or do half of them, and wait for things to settle, and then do the other half. Lots of options.You might want to read The Practice of System Administration -- <a href=

You could use a configuration management framework like Chef. Granted, it takes a bit longer to put in place as opposed to a just-get-it-done method, but the end result is something that is repeatable and, hopefully, less painful to triage.

I'd add not using a configuration management tool.

At that point you might as well use a configuration management system.

Yes, I think it would be a deal breaker for me personally. For the one thing, there would be a bit of effort to migrate from any config management system (my background is Chef and Ansible) to straight bash scripts. Also, it doesn't allow for the modularity and reusability of scripts that these services grant you. In fact, if you really want to make this simple, adding support for config management as crucial. I can easily import a Chef cookbook, override a couple attributes and have a MySQ

You can use a configuration manager like Puppet.https://en.m.wikipedia.org/wiki/Puppet_(software)

You can use some sort of configuration management tool to manage most of that from one centralized place. Some examples are chef, puppet, ansible, etc.I recommend ansible since it's pretty lightweight and uses plain old ssh (i.e.: no agent daemon required). You can setup some simple playbooks or run some tasks remotely on one or multiple servers at the same time.These tools are very flexible but they do require a bit of a learning curve so it may not be worthwhile for 2 servers. It&#x

Because you are managing your servers as pets not cattle? Because you did the installs manually and can't replicate them? Thats what you need to fix, with automated deployments that is a non issue.

Does no one in HN understand the basic concepts of configuration management?