Closed tomjn closed 2 years ago
❯ vagrant up --provision
__ __ __ __
\ V\ V\ V / v3.10.0 Ruby:2.7.4, Path:"/Users/tarendai/dev/vvvwpdev"
\_/\_/\_/ git::develop(a5db7c29)
Platform: darwin19 shell:/bin/bash vagrant-goodhosts vagrant-vbguest shared_db_folder_disabled
Vagrant: v2.2.19, virtualbox: v6.1.24
Docs: https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard: http://vvv.test
The provisioner log file:
I have this same issue after updating Stable Branch to 3.9.1 and provisioning Trunk.
% git rev-parse stable
fabccb8eda5d6dfb1ba1c130ecaedda1143fb161
@alana29s I actually fixed it at my end not long after creating the issue and made commits, switch to the develop
branch and try again.
Note that you only need wordpress-develop
if you're contributing to WordPress core itself. If you want to build plugins and themes, do client work, or work on a personal site, you should not be using that provisioner and use custom-site-template
instead
Main goal right now is confirming the fixes work for other people
This PR was what fixed things in VVV core, and changes to the develop site template should be in there already. Checkout the latest develop
branch to test
@tomjn I had found in the past that the Trunk branch had to be provisioned for PHP Unit to be installed. I do have a custom site provisioned in addition to the templates included with VVV.
I haven't used PHP Unit in VVV for a while and am working to get it setup again for a current project. My notes show that I used Composer Autoloader in /usr/local/src/composer/vendor/autload.php
.
I'll try the develop branch and let you know how it works out.
Also, I'm hoping to begin contributing to core in the near future 😄
@tomjn all set with provisioning the develop site. The latest develop
branch works for me. However, I'm still unable to setup PHP Unit in PHP storm and have brought that question to Slack. Thanks.
you can set up PHPUnit either on the host or by using the phpunit
that WordPress trunk installed. Installing phpunit
globally is not best practice and we stopped doing that a long time ago.
Since wordpress-develop
now provisions I'm going to close this out
If you provision the default
wordpress-trunk
that comes with VVV on a fresh install and visit the site, you get this:I expected to see the WP homepage.
Provisioning showed these: