Add example of starting PSES in a script to readme #1932
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems Solved:
Shell Hang:
Executing pwsh with the original command (the older one on top) from the readme causes shells to hang.
Not script or automation friendly.
Poor Doc Readability
The arguments list is also long enough to scroll off the screen on most devices.
Spacing them out over an array is a screen-friendly alternative.
PR Summary
Added an automation-friendly powershell script for starting the service that doesn't hang the shell.
PR Context
The original command is long (longer than the width of most device screens), so it's not great in documentation, since it needs to be readable. The old one is being left there, so that users have access to a quick and easy copy-and-paste one-liner.
It also hangs the shell. If you run it from the command line, you have to wait for the process to exit before running anything else. Since some users may want to automate the service from PowerShell itself, it is a better practice to call the command with
Start-Process
instead.