Closed ajitbohra closed 7 years ago
Hi @ajitbohra,
I came across this problem myself. I believe it is due to the new way that provisioning is handled for VVV. The current installation guide on this repository seems out of date. What you can try is cloning VVV then in that copy create a new git branch git checkout -b wp-meta-environment
. Once you have done that simply edit the vvv-config.yml
file to look more like this:
---
sites:
wordpress-default:
repo: https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-default.git
hosts:
- local.wordpress.dev
wordpress-develop:
repo: https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-develop.git
hosts:
- src.wordpress-develop.dev
- build.wordpress-develop.dev
wordpress-meta-environment:
repo: https://github.com/WordPress/meta-environment.git
hosts:
- wp-meta.dev
#wordpress-trunk: https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-trunk.git
#multisite: https://github.com/Varying-Vagrant-Vagrants/vvv-multisite.git
utilities:
core:
- memcached-admin
- opcache-status
- phpmyadmin
- webgrind
Then you can run vagrant up --provision
. Notice how the wordpress-meta-environment has been added under sites to the YAML. This at least worked for me, maybe something else is going on with your set up.
The current vvv-config.yml
file already contains the lines for wordpress-meta-environment
. It only needs to be uncommented before provisioning.
See: https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/vvv-config.yml#L28-L29
@BE-Webdesign @kevinwhoffman thank you guys finally got vvv working started from scratch following each step carefully & as suggested by @kevinwhoffman uncommented lines for WordPress meta environment and it's now working fine :)
Thanks a lot for the help guys
Followed the instruction to setup "VVV" & "WordPress Meta-Environment" on visiting wp-meta.dev its shows vvv default page!