Re: [ansible-project] Ansible book

[Michael DeHaan]

Not to my knowledge.

I think in general tech docs go out of date pretty quick, so we prefer
to collaborate around the central documentation where we can.

A book would be awesome to see though, but would always be behind on
the latest features.

We do take a hard stand on backwards compatibility, of course, so the
stuff printed would keep working.



On Thu, Mar 28, 2013 at 8:57 AM, João Paulo Mafra <jpmne...@gmail.com> wrote:
> Hi!
>
> Anyone knows if there is any book about Ansible or if someone is writing a
> book on it?
>
>
> Thank you very much!
>
> João Paulo
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-proje...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Michael DeHaan <mic...@ansibleworks.com>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/

[Nicolas G]

I just found this one in case you are still interested :

https://www.packtpub.com/ansible-configuration-management/book

[Michael DeHaan]

I haven't read this one, but my natural inclination is that these could get out of date reasonably quick.

I'd still encourage people to start with the official docs (and contribute to the official docs) versus someone thinking they should need an external book.

It's not too hard to get started and things were written with that view in mind.

Folks should definitely look to Galaxy, ansible-examples, and the Guide section of the docs also.

--

You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Jeff Geerling]

Just wanted to add in another update (in case OP is still following this thread); I'm halfway through a new book on Ansible, Ansible for DevOps. My aim is to take developers and sysadmins who may or may not be using any automation for their infrastructure, introduce Ansible and infrastructure automation, and keep things short enough to be readable but long enough to be meaningful.

Instead of publishing with a traditional publisher, I'm using LeanPub, which allows me to publish updates as I write them. When I started on the book, Ansible's latest release was 1.3.x, and it's now almost 1.7.x. Whenever there are large changes, or when one YAML syntax style starts becoming a de facto standard, I update the book and incorporate those changes.

In the long run, my goal is to always have the published edition of the book match the latest version of Ansible, and it's actually not too hard to do that using LeanPub :)

I'd also like to echo Michael's point about referring first to the docs; Ansible's documentation has improved radically since I started using Ansible, and you can really go from 0 to 60 on the main docs. I'm hoping Ansible for DevOps can then take you from 60 to 100 in a decent amount of time :)

-Jeff Geerling