From 3f921be93b133fa3542b47ab3bd5ba7cd6ddeeaf Mon Sep 17 00:00:00 2001 From: Ofer Nave Date: Tue, 1 Apr 2014 17:31:14 -0400 Subject: [PATCH] documented VAGRANT_DOTFILE_PATH --- website/docs/source/v2/other/environmental-variables.html.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/docs/source/v2/other/environmental-variables.html.md b/website/docs/source/v2/other/environmental-variables.html.md index 69f1645e9..9e0982cdc 100644 --- a/website/docs/source/v2/other/environmental-variables.html.md +++ b/website/docs/source/v2/other/environmental-variables.html.md @@ -20,6 +20,10 @@ expanded relative to where the Vagrantfile is found. This environmental variable is most commonly set when running Vagrant from a scripting environment in order to set the directory that Vagrant sees. +## VAGRANT\_DOTFILE\_PATH + +`VAGRANT_DOTFILE_PATH` can be set to change the directory where Vagrant stores VM-specific state, such as the VirtualBox VM UUID. By default, this is set to `.vagrant`. If you keep your Vagrantfile in a Dropbox folder in order to share the folder between your desktop and laptop (for example), Vagrant will overwrite the files in this directory with the details of the VM on the most recently-used host. To avoid this, you could set `VAGRANT_DOTFILE_PATH` to `.vagrant-laptop` and `.vagrant-desktop` on the respective machines. (Remember to update your `.gitignore`!) + ## VAGRANT\_HOME `VAGRANT_HOME` can be set to change the directory where Vagrant stores