#Keytouch ubuntu 14.04 install#
#Keytouch ubuntu 14.04 password#

Outputansible-playbook playbook.yml -i hosts -u sammy -K Our inventory is very simple.Īdd the line for, and below it, the IP address of your wordpress-server: We can run our playbooks for the servers or groups of servers defined in our inventory file ( hosts).

#Keytouch ubuntu 14.04 install#

Inventory (hosts file)Īn Ansible inventory informs Ansible about what servers we have that we want to install WordPress on. In this section, we’ll write the commands to install WordPress on our remote server. For the most part we will be concerned with each role’s tasks/main.yml file.Īt this point we should have the following file structure: This is in accordance with Ansible’s best practices. You’ll notice that this creates a whole file structure for each of our roles. For each role that we want to create, we will run ansible-galaxy init: We can bootstrap our roles with an Ansible tool called ansible-galaxy. For this project we’ll create four roles:įrom the project root folder ( ~/wordpress-ansible), create a directory called roles and cd into it: You can think of roles as re-usable modules. It is best practice to split our playbooks up into roles. mkdir wordpress-ansible & cd wordpress-ansibleĬd into this directory and create two files: one called playbook.yml (this is where we’ll write the commands to install WordPress) and another called hosts (this tells Ansible on which servers to run the commands):.Now that we’ve installed Ansible, let’s get prepare the file structure for our Ansible playbook. You can make sure that Ansible is installed by running: SSH in to your build-server and run this command to install Ansible: In this section we’ll install Ansible on your build-server. ansible-playbook playbook.yml -i hosts -u sammy.

#Keytouch ubuntu 14.04 password#

Now, throughout this tutorial, you can run the ansible-playbook commands without the -K flag, so you don’t have to enter the sudo password manually. Once you’ve done this you should be able to execute the following command on the wordpress-server without supplying a password: This will verify your changes before saving the file - this can save you from accidentally locking yourself out of the machine completely. NB: Always edit the sudoers file using the visudo command. It is important that this is the last line, otherwise it will be overridden. This has to be the last line in the file. Type visudo to edit the sudoers file:Īdd this line at the end: sammy ALL=(ALL) NOPASSWD: ALL To give our sudo user on the wordpress-server this privelege, we’ll need to edit the sudoers file. It is faster but less secure to use passwordless sudo access on your wordpress-server.

You should run the tutorial from your build-server and upload the key to your wordpress-server You can set this up by following this tutorial.

Add the SSH key of your build-server sudo user to your wordpress-server’s sudo user’s authorized_keys.

Sudo non-root users configured for both servers.

We will install WordPress (via Ansible) on this server (referred to in this tutorial as the wordpress-server) We will log into this server, and all the files and commands for this tutorial will be run on this server

We will install Ansible on this server (referred to in this tutorial as the build-server). In order to complete this tutorial, you will need to have the following set up: We will use two servers: A build server running Ansible, and a target server on which we will install WordPress using Ansible. We will install WordPress more or less according to the process outlined in this tutorial, but automatically.

With a few lines of YAML (a straighforward markup language), we will automate the typically tedious process of setting up WordPress on a fresh Ubuntu 14.04 server. If you find yourself deploying WordPress over and over again, Ansible could save you a lot of time. Ansible is a simple, agentless way to automate your infrastructure.