Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support using other ports? #5

Open
joamatab opened this issue Jun 9, 2023 · 2 comments
Open

support using other ports? #5

joamatab opened this issue Jun 9, 2023 · 2 comments

Comments

@joamatab
Copy link
Contributor

joamatab commented Jun 9, 2023

for developer containers in docker

how about allowing to set the port that it uses?

image

@sebastian-goeldi
@SkandanC
@tvt173
@Jan-David-Black

@sebastian-goeldi
Copy link
Collaborator

I have thought about it recently. I think the best way is to add a GUI element that allows you to set additional IPs and the port to listen on. I have to say for me this is low-prio though as I have no intention of using a non-standard port and even less desire to write another GUI dialog in klayout, as those are always a pain to write.

@jan-david-fischbach
Copy link

I have also been thinking about this: we might as well just check a range of ports for mqtt brokers from the translator side. (and subscribe to all of them?). Like this we can at least avoid problems with a couple of dev containers being connected at the same time, causing the port forwarded to to increment automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants