On Fri, 2017-07-21 at 07:31 +0100, Peter Robinson wrote: > > Keep in mind that Ansible is also something small-scale admins > don't use. It > > only makes sense at all if you have at least 2 servers, and it is > only > > really worthwhile if you have several, mostly identical servers. If > you have > > just one server, or two or three servers with very different > configuration > > from each other, it's just not worth it. So the workflow you > suggest > > introduces an extra learning curve. > > Actually I disagree with you, I know people that use ansible to > manage > their laptop config (IE a single device) so that if they rebuild it > they can get all their configs back quickly. I agree with Peter, and I'll add another reason why Ansible is still useful even if you only manage one system with it: it's a nice way to describe everything that is different about your server from a clean install (as code in git, so you can also get history). I find it helpful to be able to answer the question "what is customized on this system?"
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
