OK. Well I setup an empty Ubuntu 14.0.4 droplet at Digital Ocean. Did not add keys yet, but can do so later and understood that you do not need it right away to deploy with Ansible. Wanted to test if I can setup Bedrock on that server using the Ansible setup.
In site.com/wprmote.com/ansible/group_vars/ I configured the development and production files. Running vagrant locally after the the intial setup as followed at https://github.com/roots/bedrock-ansible went well:
vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'roots/bedrock' is up to date...
==> default: Resuming suspended VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection refused. Retrying...
==> default: Machine booted and ready!
==> default: Checking for host entries
Then I tried
./deploy.sh production site.com
and hit a snag
PLAY [Deploy WP site] *********************************************************
GATHERING FACTS ***************************************************************
fatal: [xxx.xxx.xx.xxx] => SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue
TASK: [deploy | Initialize] ***************************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/Users/jasper/deploy.retry
xxx.xxx.xx.xxx : ok=0 changed=0 unreachable=1 failed=0
Using -vvv is perhaps possible running ssh, but not this script.
Checking out https://github.com/roots/roots-example-project.com/blob/master/ansible/group_vars/production now. Seems I am missing stuff in my production file…