separate client configuration of server and domain
This is a feature request.
It would be nice to be able to configure which host should be used to connect to the expose server and which base domain should be used to generate the links displayed client-side.
Example:
-
https://*.example.comresponds with the expose server -
https://expose.example.comshows the admin backend -
https://example.comdoes not respond with the expose server but with a webpage
An easy workaround to still use expose is setting something.example.com as the host. This will work and correctly set up the forward. Unfortunately the client now tells me I can connect to https://jfh347y78y.something.example.com while https://jfh347y78y.example.com would be correct. That's why optionally setting the base domain would be practical.
I can PR a solution if you like.
I would like this as well, hoping for a PR from you, @dakira
I tried looking into it myself, but must admit I am simply unable to distinguish between
- domain
- sharedUrl
- host
- hostname that is used throughout this application - and sometimes changing from hostname to host or vice versa through the function calls.
@MithrandirDK hey. I'll wait for @mpociot to comment before working on a PR.
Closing this issue because it's old 🙈