hello in my particular use, i have a mac mini and a linux box, where everything I use is on dropbox
so at ~/.vagrant.b/Vagrantfile of each home user i mount there the dropbox folder to every machine, as the path is different. in that way any machine always will have /Dropbox for me. other way, is the path is always the same, you can set a sync folder with relative path, like ../shared_folder in all the vms On Mon, Jun 2, 2014 at 2:38 AM, Glen Mailer <[email protected]> wrote: > That's not something I'd considered - I'd like to keep the two in sync > where possible, but that's certainly doable in the system you suggest with > a symlink. > > I'll give this a go > > Thanks! > > On Monday, 26 May 2014 23:03:25 UTC+1, Alvaro Miranda Aguilera wrote: >> >> Hello >> >> What stop you copying the same Vagrantifle or folder several times say >> >> folder_virtualbox >> folder_aws >> >> and have each one for one provider? >> >> >> >> On Tue, May 27, 2014 at 4:43 AM, Glen Mailer <[email protected]> wrote: >> >>> I've found myself a couple of times wanting to create a machine on more >>> than one provider at the same time >>> >>> This is useful when you want to test that the Vagrantfile can be used >>> with different providers, or when you build a local VM to make changes, but >>> switching to a cloud provider to make your new box public. >>> >>> But when you try to do this, vagrant says: >>> >>>> Vagrant currently allows each machine to be brought up with only a >>>> single provider at a time. A future version will remove this limitation. >>>> Until then, please destroy the existing machine to up with a new provider. >>>> >>> >>> At this point, rather than destroy the active machine, I cheat. I just >>> rename the machine's folder inside ./.vagrant >>> >>> mv .vagrant/machines/default .vagrant/machines/default_virtualbox >>> vagrant up --provider=vmware_fusion >>> mv .vagrant/machines/default .vagrant/machines/default_vmware_fusion >>> mv .vagrant/machines/default_virtualbox .vagrant/machines/default >>> >>> After doing this a few times I decided that i'd better wrap the renaming >>> up in a script before I really broke something >>> >>> I case anyone else finds this useful, the plugin is available at >>> https://github.com/glenjamin/vagrant-provider >>> >>> It provides a `list` command, to find all renamed machine folders >>> It provides a `stash` command, to rename the current machine folder >>> And it provides a `pick` command, to rename a stashed folder back into >>> the real one. >>> >>> There is also some sanity checking to try and make sure you don't >>> clobber anything important. >>> >>> NOTE: I expect this approach to be entirely not recommended by the >>> vagrant core team, but it does just rename files with a bit of validation >>> checking. Hopefully it is a useful stopgap until the real version of this >>> functionality makes it upstream. >>> >>> >>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
