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
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
The issue:
I just did a new vv create today and all my vv sites stopped working. When I vagrant up, I see that only the defaults get added to the host file. So, all my previous vv sites are no longer added.
I didn't know how VVV worked in regards to updating the hosts file, but I guess it updates vvv-config.yml (or in the code it seems to make a copy called vvv-custom.yml). I don't see a vvv-custom.yml file and my vvv-config.yml just has the defaults.
I got around the issue by manually updating the vvv-config.yml, but something seemed to happen. After that I updated VVV and VV, the issue still persists, so something has changed?
Side note, I was one of the users who had to vagrant ssh and run the vvv-init.sh script because for whatever reason it would not work outside the VM.
The text was updated successfully, but these errors were encountered:
system info
MacOS Sierra 10.12.5
version
1.12
debug output
/usr/local/bin/vv: line 1481: version: command not found
vv: /usr/local/bin/vv
vv_config: /Users/tarik/.vv-config
vvv path: /Users/tarik/dev/VVV/
home: /Users/tarik
tput:
cat: /bin/cat
curl: /usr/bin/curl
brew: /usr/local/bin/brew
tar: /usr/bin/tar
find: /usr/bin/find
git: /usr/bin/git
sed: /usr/bin/sed
paste: /usr/bin/paste
vagrant: /usr/local/bin/vagrant
The issue:
I just did a new
vv create
today and all my vv sites stopped working. When Ivagrant up
, I see that only the defaults get added to the host file. So, all my previous vv sites are no longer added.I didn't know how VVV worked in regards to updating the hosts file, but I guess it updates
vvv-config.yml
(or in the code it seems to make a copy called vvv-custom.yml). I don't see avvv-custom.yml
file and myvvv-config.yml
just has the defaults.I got around the issue by manually updating the
vvv-config.yml
, but something seemed to happen. After that I updated VVV and VV, the issue still persists, so something has changed?Side note, I was one of the users who had to
vagrant ssh
and run thevvv-init.sh
script because for whatever reason it would not work outside the VM.The text was updated successfully, but these errors were encountered: