@swalkinshaw Did you get a chance to create an example Vagrantfile showing how to provision to DO? Im about to take the plunge myself so any help would be very much appreciated.
Trying to get this to work with the new box… for some reason I’m getting the error when I’m running the ansible provisioner. I recently upgraded to Mavericks but I cannot find anything about needing to change anything with ansible or how to fix this error… any ideas? I’ve been googling this error and coming up with nothing about how to change the path for ansible. I’ve verified it’s installed with homebrew and up-to-date.
==> default: Running provisioner: ansible...
The executable 'ansible-playbook' Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
UPDATE: I needed to do a brew uninstall ansible and then re-install it. For some reason brew update was not upgrading ansible to it’s latest version. After re-installing I was able to access it via the command line also with ansible --version(1.6.1) so I know it’s working now.
Performing a vagrant up now runs through the process fine.
I’ve done it with this Vagrantfile: https://gist.github.com/swalkinshaw/fcb08adfaf86a4be0806
You need this plugin installed: https://github.com/smdahlen/vagrant-digitalocean and the proper DO env vars set up as seen in the Vagrantfile for api keys etc.
But it requires more configuration that I don’t have right now. The prod box references a new prod.yml playbook instead of the normal site.yml. It’s basically the same but doesn’t run the wordpress-sites role.
So the steps would be something like this:
- Run
vagrant prod up --no-provision - Create a prod specific
prod.ymlplaybook with the roles you want - Create a new
hostsfile with a[wordpress-server-prod]group and the DO ip/host - You could move the
group_vars/allto be env specific atgroup_vars/wordpress-server-prodandgroup_vars/wordpress-serverif you only want those vars to apply to each server - Run
vagrant prod provision - Update Capistrano configs with the correct prod ip/host
- Run
cap production deploy
The steps are something like that…
Honestly I don’t think production servers should be managed with Vagrant. Maybe if you want a remote dev server. I’d probably just set up the servers manually (if you only have 1 per site or 1 total) and then run ansible-playbook -i prod.yml hosts manually.
Thanks for that Scott. That makes sense will give it a go for a remote staging/dev server. For production are you saying essentially set up the server manually but provision it with ansible?
Correct. Then you can look into just doing everything with Ansible. It has a built-in Digital Ocean module to manage servers.
If I wanted to have more than one site on the Box, how would I change the hosts file on bedrock-ansible, /etc/hosts and the group_vars/all file? I tried adding a new IP address for each in the hosts file and the /etc/hosts file but I’m not sure if that’s the correct way… do you have an example of this?
All you need to change is adding another site “item” in group_vars/all. See this Gist: https://gist.github.com/swalkinshaw/12ab5364a41eacfee208
wordpress_sites is just an array.
The hosts file is the remote servers. So adding another IP/host there actually means you have another remote server/VM.
I downloaded the bedrock-ansible and bedrock repos into the following locations:
/Users/btamm/Sites/brandontamm/bedrock-ansible
/Users/btamm/Sites/brandontamm/example.dev
I followed the instructions from bedrock-ansible, set the vagrant file and group_vars and try to run ‘vagrant up.’ Everything works as supposed to, the machine boots, mounts shared folders, and then ttys to run provisioner: ansible and I receive the following error message:
The executable ‘ansible-playbook’ Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
I have tried every variation of adjusting the path:
ansible.playbook = './bedrock-ansible/site.yml’
ansible.playbook = './site.yml’
ansible.playbook = '…/bedrock-ansible/site.yml’
ansible.playbook = ‘…/site.yml’
I am assuming the error has something to do with my path. I made no adjustments to site.yml and have not moved it from the original location. Am I missing something?
That error message just means that the executable ansible-playbook couldn’t be found. Did you install Ansible first? If running ansible-playbook doesn’t work in your terminal, then it won’t work through Vagrant either.
**SOLVED! Thanks again Scott.
Can’t tell you enough how much I appreciate the work you guys do. You guys are revolutionizing developer workflow!
Also - I like the Bedrock and Ansible setup, however, 2 questions.
- Have you looked into using Docker vs. Vagrant/Ansible?
- Reasons for choosing Vagrant over Ansible?
- Future plans for Docker?
Anyways, keep up the good work and NO HURRY in getting back to me. Cheers!!
Glad you’re enjoying everything 
-
Not too much yet. Docker is awesome but probably not needed in most basic server setups (which WP sites often are)
-
Well we’re using both of them? Didn’t choose one over the other. Vagrant is meant for development environments so that’s what we’re using it for. And Ansible for server provisioning.
-
Probably not anytime soon.
The VM that is created is 512 mb. My macbook runs with 8gb ram. - is there a variable I can change to increase the amount of dedicated ram to the virtual machine?
See question #3 and my answer in this thread: Php error when app/themes or app/plugins directories are not empty
I’m a little bit confused here–does this mean I can run multiple sites from a single Bedrock Ansible project simultaneously, like one would with MAMP and virtual hosts? If that’s the case, I may be missing something.
Setting up my group_vars/all file as instructed above works until Composer runs, which throws this error:
stdout: Composer could not find a composer.json file in /srv/www/example.dev/current
My Vagrantfile is pretty minimally modified:
config.vm.network :private_network, ip: '192.168.50.5'
# config.vm.hostname = 'example.dev' # This is taken care of via /group_vars/all, right?
# adjust paths relative to Vagrantfile
config.vm.synced_folder '../sites', '/srv/www', owner: 'vagrant', group: 'www-data', mount_options: ['dmode=776', 'fmode=775']
My impression was that the synced folder would be your/sites/dir instead of your/sites/dir/specificsite.dev. But it doesn’t look like Vagrant is seeing my development files at all. What am I doing wrong here?
Yeah, config.vm.hostname isn’t really needed but should probably be set to something. Could just be sites.dev or something for identification purposes.
Right now you need to explicitly set up every individual site as a synced folder.
config.vm.synced_folder '../sites/site1', '/srv/www/site1/current', owner: 'vagrant', group: 'www-data', mount_options: ['dmode=776', 'fmode=775']
config.vm.synced_folder '../sites/site2', '/srv/www/site2/current', owner: 'vagrant', group: 'www-data', mount_options: ['dmode=776', 'fmode=775']
Ohh. Duh. Well there’s my problem. I thought I tried adding multiple synced folders and it only found one of them, but it probably failed on the first one because my directory structure was bad.
I’ll try it as soon as I’m back at the ole desk, though I’m strongly considering keeping one VM per project.
Just a note that I’ve committed a fix for the admin slowness/update errors: https://github.com/roots/bedrock-ansible/commit/38c32986ebe2c73df02ab86688f43c12c6bab431
Is it safe to assume that this Ansible playbook is secure for provisioning a production server? It sounds like you use it yourself for this, but just wondering what your thoughts are.
The only other things you’d need for production are:
- Root MySQL pw
- Maybe firewall/fail2ban rules or SSH lock down
- WP caching plugin