From 9bbf49f3ff51a48cc193599c4539479715717a0c Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Thu, 10 Apr 2014 10:51:25 -0700 Subject: [PATCH] website/docs: multi-machine autostart --- .../docs/source/v2/multi-machine/index.html.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/website/docs/source/v2/multi-machine/index.html.md b/website/docs/source/v2/multi-machine/index.html.md index e105c0f55..6c220bfbe 100644 --- a/website/docs/source/v2/multi-machine/index.html.md +++ b/website/docs/source/v2/multi-machine/index.html.md @@ -106,3 +106,20 @@ config.vm.define "web", primary: true do |web| # ... end ``` + +## Autostart Machines + +By default in a multi-machine environment, `vagrant up` will start +all of the defined machines. The `autostart` setting allows you to tell +Vagrant to _not_ start specific machines. Example: + +```ruby +config.vm.define "web" +config.vm.define "db" +config.vm.define "db_slave", autostart: false +``` + +When running `vagrant up` with the settings above, Vagrant will automatically +start the "web" and "db" machines, but will not start the "db\_slave" machine. +You can manually force the "db\_slave" machine to start by running +`vagrant up db_slave`.