From c4c8dbc888d6c0eae586ea39c59c4b2a19462ebd Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Fri, 11 Apr 2014 18:33:12 -0700 Subject: [PATCH] website/docs: clarify command line for multi-machine --- website/docs/source/v2/multi-machine/index.html.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/website/docs/source/v2/multi-machine/index.html.md b/website/docs/source/v2/multi-machine/index.html.md index 121a83518..e105c0f55 100644 --- a/website/docs/source/v2/multi-machine/index.html.md +++ b/website/docs/source/v2/multi-machine/index.html.md @@ -68,11 +68,14 @@ The moment more than one machine is defined within a Vagrantfile, the usage of the various `vagrant` commands changes slightly. The change should be mostly intuitive. -Most commands, such as `vagrant up`, begin requiring the name of the machine -to control. Using the example above, you could say `vagrant up web`, or -`vagrant up db`. If no name is specified, it is assumed you mean to perform -that operation on every machine. Therefore, `vagrant up` alone will bring -up both the web and DB machine. +Commands that only make sense to target a single machine, such as +`vagrant ssh`, now _require_ the name of the machine to control. Using +the example above, you would say `vagrant ssh web` or `vagrant ssh db`. + +Other commands, such as `vagrant up`, operate on _every_ machine by +default. So if you ran `vagrant up`, Vagrant would bring up both the +web and DB machine. You could also optionally be specific and say +`vagrant up web` or `vagrant up db`. Additionally, you can specify a regular expression for matching only certain machines. This is useful in some cases where you specify many similar