Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Need a complete example for how to use the --proxy-domain feature ...

See original GitHub issue

Hello Friends:

I’ve been searching for, as well as playing with the --proxy-domain feature of code-server(1), but I can’t yet understand how to use it. I suspect it may be useful for my use-case, but need a complete example of how to use it. Can friends here provide a multi-user / multi-instance example illustrating how each connecting user would get routed to it’s awaiting code-server(1) instance?

Thank you in advance. (◠﹏◠)

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

code-ashercommented, Jun 30, 2020

No problem! I’ll go ahead and close the issue but please feel free to drop more questions here. If you happen to have any ideas on improving the FAQ entry let me know as well.

0reactions

nmvegacommented, Jun 30, 2020

In this case I think you would run code-server with something like:
code-server --host 0.0.0.0 --port $UID --proxy-domain $UID.domain.tld
Then if I’m user 5001 for example I can access code-server at 5001.domain.tld and I can also access my development servers at <port>.5001.domain.tld.

That’s what I suspected but needed a little hand-holding to be certain. =:) Thank you.