-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show VM status in Tart list #300
Comments
I guess we might be able to see if some VM files are locked to kind of figure out if a VM is running similar to tart/Sources/tart/Commands/Run.swift Line 132 in fb954b7
|
I spotted that, I didn't think it would be relevant though given it only runs in a VNC check, and vagrant environments are normally headless, so a more universal solution seemed appropriate |
Of note it would be helpful to know the following states:
It might make sense to note this down in a file alongside the VM |
Will having just running/stopped be sophisticated for the first iteration? Just running/stopped seems doable with minimum changes to Tart. IMO the goal should be to make as less changes to Tart as possible for the first PoC for the plugin. If everything will work and the Vagrant integration will thrive in popularity, then we can work on improving the integration with more complex changes. |
That works, it may be necessary to spoof the startup state but I’d advise a
failure state even if there aren’t many places that trigger it.
…On Tue, 8 Nov 2022 at 20:08, Fedor Korotkov ***@***.***> wrote:
Will having just running/stopped be sophisticated for the first iteration?
Just running/stopped seems doable with minimum changes to Tart. IMO the
goal should be to make as less changes to Tart as possible for the first
PoC for the plugin. If everything will work and the Vagrant integration
will thrive in popularity, then we can work on improving the integration
with more complex changes.
—
Reply to this email directly, view it on GitHub
<#300 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOLZ4INOWNRIHWVAYV6M3WHKXNDANCNFSM6AAAAAARXJKXWQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Tart list currently displays the source and name for VMs but it doesn't indicate if the VM is currently running or not, or if the VM has been created.
For example, if I run this commands:
But leave out the last command, I have a bare VM that has not been run,
tart list
should show this.It might also be that a
tart status
command would be more appropriate for this, if sotart status
andtart status ubuntu
would be very helpful commands to haveThe text was updated successfully, but these errors were encountered: