Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Status command text contains log output #206
$ winsw status
The current docs on the front page say that the status command will return one line which indicates the status of the service with values of "NonExistant", "Started", or "Stopped", which is no longer true.
Our use case is that we have automated deployment of a Spring Boot app in which we have an initial powershell step which checks the state of the service (utilizing the result of the winsw status command) and then stops it if running. There is also a final step after deployment to check for the existance of the service (again using winsw status) and install it if necessary and then start the service.
Why change the exisitng "status" command to add extra diagnostics output and potentially cause breakage for existing users when you could add an additional command such as "winsw diagnotics" or something similiar and avoid breaking anything?