Codespaces custom subdomain support?

[davidronk]

Are there plans to add custom subdomain support to codespaces?
Or is there a way to do it now?

Our app currently determines the tenant via the subdomain: tenant.app.com so it would be great if we could define (or allow *) subdomains for the public forwarded ports that codespaces exposes.
So in addition to: <user>-<org>-<repo>-<code>-<port>.githubpreview.dev
we could also have: <tenant>.<user>-<org>-<repo>-<code>-<port>.githubpreview.dev

[asciimike]

I don't believe there is a way to handle this at present, and I don't think we could easily handle it (I assume signing certs for *.<user>-<org>-<repo>-<code>-<port>.githubpreview.dev is a pain, though maybe https://letsencrypt.org/docs/faq/#does-let-s-encrypt-issue-wildcard-certificates solves that?).

I will say we have considered custom domain support (so you could run <user>-<org>-<repo>-<code>-<port>.company.tld, though this isn't quite what you're looking for, and is potentially an easier problem to solve on our side).

[billiegoose]

Just want to chime in we at Stoplight.io were also testing out CodeSpaces when they first came out, and subdomains proved our stumbling block. The first thing a new user does is create a "workspace" with our product, like your-workspace.stoplight-local.com. I'm tempted to re-engineer all our routing to support an alternate code path that doesn't relyl on subdomains just so we can use CodeSpaces, but it would be wonderful to support the tenant pattern so well-described by davidronk above out-of-the-box.

[Chuxel]

If you are using VS Code locally, you can forward the port to localhost and then update your hosts file to simulate this. If you've got your own SSL certificate, you can leave the port type as blank (or HTTP) and that cert will come across. You can also disable this setting in your VS Code settings if you prefer.

[PZiaugra]

We still don't have native support for this functionality?
I tried to do according to @Chuxel comment above but I didn't get success.
My scenario is very similar to @wmhilton.

[mattvb91]

Would love to have this too. I am working on a multi tenant stack and it requires subdomains. I can forward ports locally etc.. but it would be nice to just have this ability directly inside of codespace

[waynetheisinger]

I would also like this - we would love to use codespaces for easy developer onboarding and teaching them how to port forward a bunch of subdomains is another onboarding task... we'd love to just have them be able to intuit how to get up and running with very few instructions

[neoramos]

This is something I would like as well.

[serge-salamanka]

+1 for this feature. we have a stack of applications that rely on subdomain

[wjurkowlaniec]

would be great and allow testing oauth2 apps

[Drowze]

We have a multitenant application reliant on subdomains. This is definitely one of the biggest drawbacks we have with Codespaces.

[matthiasPOE]

Has anyone managed to make progress on this?