Vagrant Environment Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 9: Line 9:
{{External|https://www.vagrantup.com/docs/cli/init.html}}
{{External|https://www.vagrantup.com/docs/cli/init.html}}


This command initializes the current directory to be a Vagrant environment by creating an initial Vagrantfile if one does not already exist.
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
  vagrant init

Latest revision as of 19:59, 17 November 2019

External

Internal

Operations

init

https://www.vagrantup.com/docs/cli/init.html

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

https://www.vagrantup.com/docs/cli/global-status.html
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