Update WP-CLI to 1.5.1

Update from `1.6.1` -> `1.7.0` which addresses roots#943 ([DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated.)

Avoids deprecation warnings introduced in Ansible 2.4:
"The use of 'include' for tasks has been deprecated."

Add xdebug.remote_autostart to simplify xdebug sessions

Because `git-core` is now a dummy package of `git`.

See: http://git.661346.n2.nabble.com/git-core-vs-git-package-on-ubuntu-tp7576083p7576085.html

Common: Install `git` instead of `git-core`

The X-Frame-Options header has been obsoleted by the frame-ancestors
directive. Retain the X-Frame-Options header for older browsers.

Return empty X-Frame-Options header for WordPress Customizer content
to prevent the conflict that SAMEORIGIN would have with the ALLOW-FROM
option that WordPress adds on its own (Safari browser).
Discussion in https://core.trac.wordpress.org/ticket/40020

In rare cases the wp_installed registered var may be missing the
stderr attribute, so add a default to avoid related error.

The `wp core  is-installed` command return code is 1 if WP is simply
not installed. However, in rare cases the command may return some
other return code indicative of true failure, so fail if rc > 1.

- Exit with `127` when not enough arguments
- Exit with `1` when hosts file not exist

See: http://www.tldp.org/LDP/abs/html/exitcodes.html

* Bump Ansible version_tested_max to 2.5.3

Convert Jinja2 tests from filter format to `var is testname` format.
Encourage users on Ansible 2.5.0 to upgrade to avoid erroneous warnings
fixed in ansible/ansible 37538

Enabled by default

Quotes prevent Ansible from interpolating the variable value as True.
True is an invalid value for fastcgi_cache_background_update and would
would make Nginx unable to reload.

Verify `wp-cli.phar` checksum

Update swapfile role

In some circumstances it is not possible to use an NFS (e.g. in combination
with ecryptfs). Allow user to configure vagrant mount type in vagrant.local.yml

build-before: Checkout project source code to local temporary directory

Configurable Vagrant mount type

… directory"

Revert "build-before: Checkout project source code to local temporary directory"

…cp forwarding, updating ip address used to form the tunnel

Update xdebug tunnel configuration

Unless you're actively debugging, the remote feature of Xdebug isn't necessary. We'll disable by default.

Disabling Xdebug requests in development

Got a little red happy in the previous commit. It was unnecessary to remove the xdebug remote defaults in development. This keeps it on for development with the ability to trigger debug requests with an HTTP param or Cookie without performance degradation.

Re-enable xdebug remote

Remove obsoleted `git` remote checking tasks introduced in roots#299
because recent Ansible versions are able to detect/handle `git` remote
changes.

See: https://discourse.roots.io/t/do-we-still-need-git-remote-checking-during-deploy/12639

…ed name on github

…ble-galaxy

roots#1011 change name of swapfile ansible requirement to match updated na…

Deploy: Remove obsoleted `git` remote checking

Fix roots#1014 (comment)

Because `synchronize` uses `sudo rsync` under the hood while `copy` doesn't
require `sudo`.

[BREAKING] Update wp-cli to 2.0.0 and verify its PGP signature

Update wp-cli to 2.0.1

Allow customizing Nginx `worker_connections`

Add output_buffering variable for PHP config

For first time users it might be useful to be explicit about which directory they should be in before running `vagrant up`, else Vagrant will display an error (`A Vagrant environment or target machine is required to run this command.`) when the `Vagrantfile` is not found.

Update README.md

Support both 2 and 3 but check for Ansible version

It no longer exists in Python 3. We can use `items()` which both have
and pipe to `list` in Jinja.

Old version was using `iteritems()` which doesnt work in Python 3

Python3 support

This fixes some more Python 2/3 compatibility issues.

Python version compatibility fixes

This was changing the interpreter/version of Python used on remote
hosts in `server.yml` to support Python 2 or 3.

However, this doesn't work in all cases yet because we're installing
Python 2 specific packages on servers.

So for now Python 3 support is limited to the host/control machine which
is the bigger issue anyway. Even Ubuntu 18.04 still defaults to Python
2.

Remove ansible_python_interpreter in server.yml

Ubuntu 18.04

Via new python_interpreter role

…erpreter

Fix Ubuntu 18.04 python interpreter

>= 2.5.3 is only required if you're running Python 3 on the host.

Fix python 3 Ansible compatibility check

Add Vagrant ssh-config to ~/.ssh/config on vagrant up

By default Vagrant runs `ansible-galaxy` with the `--force` option
causing every Galaxy role to be re-downloaded *every* time. This is
annoying, slow, and wasteful.

This customizes the `galaxy_command` to run without the `--force` flag.

Ansible 2.7 compatibility

Require Vagrant >= 2.1.0

Allow overriding rollback variables

…ults

Add `vault_wordpress_env_defaults`