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

website/docs: clarify when provisioners are run [GH-2541]

This commit is contained in:
Mitchell Hashimoto 2013-11-26 18:45:59 -08:00
parent 2092630200
commit 1156841225
2 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/source/v2/provisioning/basic_usage.html.md
View File

@ -54,8 +54,8 @@ can take over later.
## Running Provisioners
Provisioners are run in three cases: `vagrant up`, `vagrant reload`, and
`vagrant provision`.
Provisioners are run in three cases: the initial `vagrant up`, `vagrant
provision`, and `vagrant reload --provision`.
A `--no-provision` flag can be passed to `up` and `reload` if you don't
want to run provisioners. Likewise, you can pass `--provision` to force

18
website/docs/source/v2/provisioning/index.html.md
View File

@ -26,3 +26,21 @@ for provisioning.
You can find the full list of built-in provisioners and usage of these
provisioners in the navigational area to the left.
## When Provisioning Happens
Provisioning happens at certain points during the lifetime of your
Vagrant environment:
* On the first `vagrant up` that creates the environment, provisioning is run.
If the environment was already created and the up is just resuming a machine
or booting it up, they won't run unless the `--provision` flag is explicitly
provided.
* When `vagrant provision` is used on a running environment.
* When `vagrant reload --provision` is called. The `--provision` flag must
be present to force provisioning.
You can also bring up your environment and explicitly _not_ run provisioners
by specifying `--no-provision`.