3 ms·

If you would use something like Ansible it would be just as fast because it is fully automated, and there would be no work at all to change a config because Ans

If you would use something like Ansible it would be just as fast because it is fully automated, and there would be no work at all to change a config because Ansible will also customize config files from templates. Chef and Puppet and SaltStack work similarly, just learn how to use your tool of choice.

UK-AL 10y ago
And for a lot of people the tools of choice is docker...
- toomuchtodo 10y ago
  Picking the wrong tool because its easier never really scales. Docker is not configuration management. Configuration management is not containerization. Disclaimer: DevOps by day. I care because it makes it easier for me (and cheaper for you) to come in and scale things if it was done right in the beginning (instead of me having to revamp your infrastructure to move components to the right tools), but either way I get paid, so it doesn't matter much to me. I'm just trying to help make your life easier.
  - UK-AL 10y ago
    Most configuration management tools are used for managing docker on machines. I don't see them used much for setting up whats inside them. Plus they don't match the convenience of just pulling down an image identical to production for developers(very important). I also don't want to be using puppet on dev machines. Configuration management tools also take longer to run all scripts then just pulling down an image.
    - toomuchtodo 10y ago
      > I also don't want to be using puppet on dev machines. Configuration management tools also take longer to run all scripts then just pulling down an image. Which is why you should be provisioning with Vagrant locally to properly replicate production.