Only configure the hosts file if a domain is set
Change shebang to 'env sh'
Untrack wp-cli config

We can only have one config, so instead of using wp-cli.local.yml
and wp-cli.yml, we'll just use wp-cli.yml. Since we'll be editing
it with Puppet, I'm removing it from version control and Puppet
can just take care of making sure it looks good
Add command line flags to vip-init script for remote host

* `--server` sets up Quickstart locally, as if the local machine is a server
* `--domain=*` lets you define the domain from the command line
Bail if the requirements aren't available

Props @mobius5150
Switch environment back to bash (from sh)
Add Provisioning header to --server as well
Ensure the vagrant user exists and owns /srv

On remote hosts, it will be easiest just to create
the vagrant user.
Bump types_hash_max_size to 2048 to fix Nginx on Digital Ocean
Ensure the vagrant user is present
Install twentyfourteen from the wp directory
Vagrant user should own the wp-content directory

We only need the vagrant user to own the wp-content
directory so uploads work
Don't set permissions on /srv/www in Puppet

Setting permissions in Puppet has proven to be slow
so we'll do it in the VIP init script instead. This
doesn't need to happen in Vagrant since these files
are already owned by the vagrant user, so an added
bonus is that we're only doing this when necessary.
Use custom domain for admin's email
Merge remote-tracking branch 'upstream/master'

Conflicts:
	puppet/manifests/sections/wp.pp