Skip to content
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

Ensure local Backend running #178

Merged
merged 3 commits into from Oct 7, 2022
Merged

Conversation

Szubie
Copy link
Collaborator

@Szubie Szubie commented Oct 7, 2022

Instead of erroring when local backend is not running, it is a more seamless experience if bravetools automatically starts the backend for you.

An additional benefit of this when using the multipass backend is that most bravetools commands will become far more responsive. It takes far less than a second to start the VM if it is already running, making all basic commands run quicker (previous checks took several seconds).

Since starting the VM is so quick, a progress spinner will not be displayed usually - a spinner will be shown only if the start command takes longer than 1 second to complete.

…ker to run than `Info` due to less commands. Remove check for backend in `ListUnits`, add to `InitUnit` when local.
…nefit of this is much faster and more responsive when VM is already running.
@idroz idroz merged commit 828c40d into bravetools:master Oct 7, 2022
@Szubie Szubie deleted the backend-running branch October 7, 2022 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants