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

global status informs about --prune 

It's not obvious from the old explanation, how to get
rid of get rid of data that "may not be completely
up-to-date".
This commit is contained in:
Aleksi Aalto 2018-05-22 15:20:40 +03:00
parent dfb2a9e823
commit fa272816ff
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
templates/locales/en.yml
View File

@ -182,9 +182,10 @@ en:
global_status_footer: |-
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
global_status_none: |-
There are no active Vagrant environments on this computer! Or,