From e7ca6acbfe6bea66ca1b7f8ebbfd6d96ff6557f5 Mon Sep 17 00:00:00 2001 From: Chris Bednarski Date: Thu, 20 Aug 2015 14:34:23 -0700 Subject: [PATCH] Revert heading change and add note about CHECKPOINT_DISABLE --- .../docs/source/v2/other/environmental-variables.html.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/website/docs/source/v2/other/environmental-variables.html.md b/website/docs/source/v2/other/environmental-variables.html.md index 7ed73f4fd..866b4369a 100644 --- a/website/docs/source/v2/other/environmental-variables.html.md +++ b/website/docs/source/v2/other/environmental-variables.html.md @@ -17,14 +17,17 @@ when launching Vagrant from the official installer, you can specify the `VAGRANT_DEBUG_LAUNCHER` environment variable to output debugging information about the launch process. -## CHECKPOINT\_DISABLE +## VAGRANT\_CHECKPOINT\_DISABLE Vagrant does occasional network calls to check whether the version of Vagrant that is running locally is up to date. We understand that software making remote calls over the internet for any reason can be undesirable. To surpress these -calls, set the environment variable `CHECKPOINT_DISABLE` to any +calls, set the environment variable `VAGRANT_CHECKPOINT_DISABLE` to any non-empty value. +If you use other HashiCorp tools like Packer and would prefer to configure this +setting only once, you can set `CHECKPOINT_DISABLE` instead. + ## VAGRANT\_CWD `VAGRANT_CWD` can be set to change the working directory of Vagrant. By