[REQUEST] Support subdomain routing

Question

[REQUEST] Support subdomain routing

require-dev opened this issue 2 years ago · comments

It would be great to support subdomain routing instead of just {domain}.stacks.run
Some projects I'm working in on use {subdomain}.{domain}.stacks.run

I'm assuming (custom) redbird resolvers would be the way forward here, but this might result in SSL certificate issues

Naba Kumar Das · Answer 1 · Thu Feb 23 2023 22:54:26 GMT+0800 (China Standard Time)

@require-dev, thanks for your valuable feedback. We will definitely look into this

Mike · Answer 2 · Fri Feb 24 2023 00:34:38 GMT+0800 (China Standard Time)

Would love to help with this, but can’t seem to get Deck running from sources on my machine.

Is there a developer guide or some steps I need to go through?
(running on M1 Mac)

Naba Kumar Das · Answer 3 · Fri Feb 24 2023 01:13:38 GMT+0800 (China Standard Time)

Hi @require-dev, Thanks for your reply, please review the installation process.

https://www.loom.com/share/20eb23519f894a33971aaedc07b45031
Appreciate your feedback here. Let us know of any issues, we'd be happy to help.

Naba Kumar Das · Answer 4 · Mon Mar 06 2023 23:31:34 GMT+0800 (China Standard Time)

Hi @require-dev,
thanks for your valuable feedback
Currently, multiple-layer sub-domain is not supported. (.sub-domain.stacks.run), only supported (.stacks.run), you can use *.stacks.run, i.e. {sub-domain}.stacks.run.

Mike · Answer 5 · Tue Mar 07 2023 21:03:04 GMT+0800 (China Standard Time)

Hi @nabad600, I've implemented a working solution locally which routes *.stackname.stacks.run to the correct stack backend in docker.

Check the pull request attached above for more info.
Downside is that, while it does support SSL, it'll give an SSL warning about the subdomain