-
Notifications
You must be signed in to change notification settings - Fork 702
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
Valet status command #251
Comments
|
@shiroamada, sent a PR to fix your issue: #268 |
It this command |
No, however, valet is more verbose about errors occurring when re/starting nginx. Nowadays you can run: |
Closing; if this is re-suggested given the current state of things we can start a new discussion. |
I think it would be really nice to have this command. |
I'm considering adding this command to v4. Here's what I'm thinking. Valet isn't ever actually "running" or "not running". But, it can have a boolean type status: it can be "configured correctly with all its services running" or "something is wrong, whether a service not running, a configuration error, or Valet not installed at all". Would that be helpful? If so, I'm imagining it would check:
If so, it would return a positive return code, together with some nice graphics showing success. If not, it would return a negative return code, together with the same graphics showing errors. |
It would be nice to have a
valet status
command, to know if valet is currently started or stopped.With this kind of command we could call it from any menu-bar software like BitBar, and get a visual indication of valet status.
The text was updated successfully, but these errors were encountered: