From 8c03b5179af0a84f8d369b0cc2473fb5a1b39d6d Mon Sep 17 00:00:00 2001 From: Greg J Preece Date: Tue, 4 Jun 2019 21:16:03 -0700 Subject: [PATCH] Correcting suggested VAGRANT_HOME location in dev. --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index bbb53c96c..e2e387dcf 100644 --- a/README.md +++ b/README.md @@ -58,12 +58,11 @@ Once your Vagrant bundle is installed from Git repository, you can run the test This will run the unit test suite, which should come back all green! -If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). In this case, override the -`VAGRANT_HOME` environment variable for your development version of Vagrant before running any commands. For example, in Bash: +If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). This can cause errors when Vagrant attempts to load plugins. In this case, override the `VAGRANT_HOME` environment variable for your development version of Vagrant before running any commands, to be some new folder within the project or elsewhere on your machine. For example, in Bash: - export VAGRANT_HOME=/path/to/project/.vagrant + export VAGRANT_HOME=~/.vagrant-dev -This folder will be ignored by Git. You can now run Vagrant commands against the development version: +You can now run Vagrant commands against the development version: bundle exec vagrant