haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update the docs to match previous change

This commit is contained in:
Carlos Rodrigues 2016-07-24 18:41:04 +01:00
parent 188a7dab0c
commit 6b49d505d4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/other/environmental-variables.html.md
View File

@ -68,7 +68,7 @@ a scripting environment in order to set the directory that Vagrant sees.
`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_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`!)
Non-absolute paths in this environmental variable are interpreted as relative to the current working directory unless prefixed with `{}` (example: `{}/.vagrant-laptop`), in which case they're interpreted as relative to the Vagrantfile. Non-absolute paths in this environmental variable are interpreted as relative to the Vagrantfile's location.
## `VAGRANT_HOME` ## `VAGRANT_HOME`