Closed (fixed)
Project:
Vagrant
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2013 at 11:26 UTC
Updated:
24 Jan 2013 at 09:09 UTC
I'm a little confused about what vagrant up does. The first time it installs everything and there is a log of it so it takes quite a long time before the vm is running. I created second vhost and drupal installation and then I did vagrant halt and vagrant up again (I wanted to use nfs shared folders here).
What is strange to me is that all the cookbooks seem to be running again like it was first time build.
Should I comment something out from Vagrantfile after first installation?
Comments
Comment #1
glennpratt commentedvagrant updoes cause a Chef run, but it shouldn't be re-installing everything, just verifying.You can also run
vagrant provisionto just run Chef instead of rebooting.Comment #2
philipz commentedThanks for clarifying! I'm having trouble with my /etc/hosts on host machine not working anymore after vagrant rebooting but this might be some misconfiguration I've made. The databases and system configurations I've done are still in place after rebooting vagrant.