Configure custom OMERO.server port #48
Open
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
|
This sounds like a good idea. However we recently added websockets to the supported protocols, and in future we might try and unify the host strings. Instead of adding a new variable would you mind making it an optional component of
|
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.
It would be useful to configure a custom OMERO.server port as you do with the OMERO.server host.
I implemented it in ome_seadragon docker image (crs4/ome_seadragon-docker@9fb2829) but I think it would be more appropriate to integrate this change into the "main" omero-web Docker image.
I needed this because I have multiple OMERO.servers running on the same Docker host and each one of them exposes ports that are different from the standard ones.