vv create --name DOMAIN_REMOVED -wv 4.5.2 --database /Users/aidan/wordpress.sql --git-repo file:///Users/aidan/wp-content --debug
New VVV Site Setup
Domain to use (leave blank for DOMAIN_REMOVED.dev):
Install as multisite? (y/N): n
Remove default themes and plugins? (y/N): n
Add sample content to site (y/N): n
About to perform the following:
* Halt Vagrant (if running)
* Create directory DOMAIN_REMOVED in /Volumes/SanDisk SDSSDA240G/wordpress/VVV/www
* Create files vvv-init.sh, wp-cli.yml, and vvv-hosts in directory DOMAIN_REMOVED
* Create file DOMAIN_REMOVED.conf in /Volumes/SanDisk SDSSDA240G/wordpress/VVV/config/nginx-config/sites
* Run `vagrant up --provision` to initialise site
Provisioning Vagrant will do the following:
* Create database DOMAIN_REMOVED
* Install WordPress 4.5.2 in the htdocs directory
* Make the site visible at DOMAIN_REMOVED.dev
Continue (y/n)? : y
[Success] New VVV setup starting for site 'DOMAIN_REMOVED'
Checking to see if vagrant halt should be run...
Vagrant not running, skipping `vagrant halt`...
Creating site directory, wp-cli.yml, and vvv-init.sh file...
Done
Adding DOMAIN_REMOVED.dev to new vvv-hosts file...
Done
Cloning into 'htdocs/wp-content'...
remote: Counting objects: 2740, done.
remote: Compressing objects: 100% (2663/2663), done.
remote: Total 2740 (delta 249), reused 0 (delta 0)
Receiving objects: 100% (2740/2740), 16.30 MiB | 8.72 MiB/s, done.
Resolving deltas: 100% (249/249), done.
Checking connectivity... done.
fatal: no submodule mapping found in .gitmodules for path 'REMOVED_PATH'
Creating nginx-config/sites/DOMAIN_REMOVED.conf...
Done
Running vagrant up --provision...
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: VirtualBox VM is already running.
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 DOMAIN_REMOVED.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 vvv.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 local.wordpress.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 local.wordpress-trunk.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 src.wordpress-develop.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] 192.168.50.4 build.wordpress-develop.dev # VAGRANT: 6fee070c04c2979263bd71018c7c3af1 (default) / 0cefb174-bc94-47ad-a811-6c2bbd61a350
==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> default: Running triggers after up...
==> default: Executing command "vagrant ssh -c vagrant_up"...
==> default: /home/vagrant/.bash_profile: line 36: grunt: command not found
==> default: Command execution finished.
[Success] New VVV Site Setup: Done!
Directory: /Volumes/SanDisk SDSSDA240G/wordpress/VVV/www/DOMAIN_REMOVED
URL: DOMAIN_REMOVED.dev
Username: admin
Password: password
VV Version: vv version 1.10.2 VV Debug Info:
VV Log: