Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Ansible 2.7

You're reading from   Learning Ansible 2.7 Automate your organization's infrastructure using Ansible 2.7

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789954333
Length 266 pages
Edition 3rd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Fabio Alessandro Locati Fabio Alessandro Locati
Author Profile Icon Fabio Alessandro Locati
Fabio Alessandro Locati
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Creating a Web Server Using Ansible FREE CHAPTER
2. Getting Started with Ansible 3. Automating Simple Tasks 4. Section 2: Deploying Playbooks in a Production Environment
5. Scaling to Multiple Hosts 6. Handling Complex Deployment 7. Going Cloud 8. Getting Notification from Ansible 9. Section 3: Deploying an Application with Ansible
10. Creating a Custom Module 11. Debugging and Error Handling 12. Complex Environments 13. Section 4: Deploying an Application with Ansible
14. Introducing Ansible for Enterprises 15. Getting Started with AWX 16. Working with AWX Users, Permissions, and Organizations 17. Other Books You May Enjoy

Using Ansible with Git

For the reasons that we have just seen, and because of its huge popularity, I suggest always using Git for your Ansible repositories.

There are a few suggestions that I always provide to the people I talk to, so that Ansible gets the best out of Git:

  • Create environment branches: Creating environment branches, such as dev, prod, test, and stg, will allow you to easily keep track of the different environments and their respective update statuses. I often suggest keeping the master branch for the development environment, since I find that many people are used to pushing new changes directly to the master. If you use a master for a production environment, people can inadvertently push changes in the production environment when they wanted to push them in a development environment.
  • Always keep environment branches stable: One of the big advantages of having...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image