You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When spinning up the VM with Vagrant I receive the following warning:
There were warnings and/or errors while loading your Vagrantfile
for the machine 'default'.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.
Warnings:
config.vm.customize calls are VirtualBox-specific. If you're
using any other provider, you'll have to use config.vm.provider in a
v2 configuration block.
The 'v-root' shared folders have been renamed to 'vagrant-root'.
Assuming you meant 'vagrant-root'...
The text was updated successfully, but these errors were encountered:
i think nobody is actively maintaining the vagrant configuration. if you want to have a look and send a PR to upgrade it, that would be great. i think by now we can safely assume that people are on a vagrant that understands the configuration v2.
Oh awesome, let me see what I need to do in order to provide you with a PR.
BTW, I was able to find the reason why the vagrantFile failed, wrong version of PHP. To fix that, perhaps moving the most recent LTS for ubuntu is sufficient.
When spinning up the VM with Vagrant I receive the following warning:
There were warnings and/or errors while loading your Vagrantfile
for the machine 'default'.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.
Warnings:
config.vm.customize
calls are VirtualBox-specific. If you'reusing any other provider, you'll have to use config.vm.provider in a
v2 configuration block.
Assuming you meant 'vagrant-root'...
The text was updated successfully, but these errors were encountered: