Daemon Process Manager #286
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tead. Also make the unified shell PM endpoint only listen localhost
PawelPlesniak
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enable the Process manager to run as a daemon, and the unified shell to connect to it. The target for this is v5.3.0. This fixes #212
With this PR, the unified shell can be started with
Provided there is a process manager running at
some-host:1234. That can be done onsome-hostvia:Alternatively, the process manager's port can be dynamic (0), and in that case the command
drunc-process-managerwill print out which port it is expecting traffic from (and the unified shell can connect to it in the same way).Of course, the usual command is still valid to start your own process manager: