deck [REQUEST] Support subdomain routing

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

Feb 23 '23 13:02 require-dev

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

Feb 23 '23 14:02 nabad600

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)

Feb 23 '23 16:02 require-dev

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.

Feb 23 '23 17:02 nabad600

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.

Mar 06 '23 15:03 nabad600

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

Mar 07 '23 13:03 require-dev