Hi, > Hello, > > If you want that shared folder in the machine being managed by Vagrant, > you should put that into the Vagrantfile, since when vagrant start the > machine, will clear the configuration for network, and shared folders. >
I don't want vagrant to touch that one particular folder, it is used by me to do work that doesn't envolve vagrant and I don't see why vagrant should be concerned about that folder. I also don't want that folder to exist in the Vagrantfile as the file in part of the git repository shared with other coworkers. If vagrant touches other VM settings or changes VirtualBox settings in a way that destroys them, should that be considered a bug? I mean, I had a shared folder setup before installing vagrant, I never told vagrant to remove it or change it in any way and vagrant is changing stuff outside its working area... or does this only happen with VirtualBox? I'll test the changes you suggested but this wasn't an expected behaviour and it should probably be written in the docs. Regards, Sérgio Lopes -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
