feat: add support for --socket to specify custom sockets #59
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
exdx
reviewed
Sep 6, 2022
|
For example f94db97 looks good to merge as-is |
tylerslaton
force-pushed
the
add-custom-socket-option
branch
2 times, most recently
from
1854da5
to
a78a673
Compare
tylerslaton
changed the title
tylerslaton
force-pushed
the
add-custom-socket-option
branch
from
a78a673
to
1653b6f
Compare
tylerslaton
force-pushed
the
add-custom-socket-option
branch
from
1653b6f
to
e0d2310
Compare
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.
Summary
Adding a new
--socketoption that allow users to specify custom socket locationsCloses #36