While we’ve been using Ansible for almost a year at Kinetic Cafe, I’ve been spending a lot more time with it at a personal level. A big part of it is that I tend to really like being familiar with the tools that my team uses at work and the other is because I actually have a lot of home and cloud servers running because I tend to like being familiar with the tools that the team uses at work. Ansible’s strength stems from the idea that you can ssh to a server and perform a series of tasks based on modules already built for you. At it’s core are concepts like inventories, roles, handlers, dependencies and variables but then allows users to use it in many different ways within that structure. However, this flexibility lead to chaos when I started to use it so I took some time organizing Ansible in a meaningful way for my home infrastructure.
Learning Ansible has been on my to-do list for a very long time now but I finally found the time to learn it, play with it and even write scripts to
- create a server on Vultr
- configure a server based on my preferred configuration
- deploy an Apache server and a MySQL server
- Configure the Apache and MySQL server for WordPress
- Restore my old WordPress install to the new WordPress install