Vagrant Environment Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→init) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | =External= | ||
=Internal= | =Internal= | ||
* [[Vagrant_Concepts#Environment_Operations|Vagrant Concepts | * [[Vagrant_Concepts#Environment_Operations|Vagrant Concepts]] | ||
* [[Vagrant Operations#Environment Operations|Vagrant Operations]] | * [[Vagrant Operations#Environment Operations|Vagrant Operations]] | ||
=Operations= | =Operations= | ||
==init== | |||
{{External|https://www.vagrantup.com/docs/cli/init.html}} | |||
This command initializes the current directory to be a Vagrant [[Vagrant_Concepts#Environment|environment]] by creating an initial [[Vagrantfile]] if one does not already exist. | |||
vagrant init | |||
==global-status== | ==global-status== | ||
| Line 21: | Line 28: | ||
The command does not actively verify the state of machines, it is instead based on a cache, so you may see stale results. | The command does not actively verify the state of machines, it is instead based on a cache, so you may see stale results. | ||
To refresh the cache: | |||
vagrant global-status --prune | |||
Latest revision as of 19:59, 17 November 2019
External
Internal
Operations
init
This command initializes the current directory to be a Vagrant environment by creating an initial Vagrantfile if one does not already exist.
vagrant init
global-status
vagrant global-status
This command tells the state of all active Vagrant environments for the currently logged in user:
id name provider state directory
------------------------------------------------------------------------
1a4c3f3 blue aws running /Users/ovidiufeodorov/tmp/blue
266ef17 red aws running /Users/ovidiufeodorov/tmp/red
The command does not actively verify the state of machines, it is instead based on a cache, so you may see stale results.
To refresh the cache:
vagrant global-status --prune