Websocket start with custom port #1482
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
Ryanf55
force-pushed
the
websocket-start-with-custom-port
branch
from
aba0b63 to
335e1c9
Compare
* Use a call text dialog handler to allow users to specify custom websocket output ports Signed-off-by: Ryan Friedman <25047695+Ryanf55@users.noreply.github.com>
Ryanf55
force-pushed
the
websocket-start-with-custom-port
branch
from
bee84c2 to
c104fee
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.
Purpose
Add a way to customize which port you use for the websocket server.
The default works with webtools.
Demo
Screencast.from.11-16-2024.06.18.48.PM.webm
Dependencies
#1481