<FromGitter>
<eliasjpr> @andrewc910 with a PIPE (Http::Handler) you can look at the request object and parse the domain from the host or headers
<FromGitter>
<eliasjpr> to get the subdomain
<FromGitter>
<eliasjpr> from within the pipe you can then add a request variable that holds the subdomain or load setting etc
<FromGitter>
<andrewc910> @eliasjpr From there, how do you check if a certain route exists? If the router doesn't register what routes are apart of what subdomain, how do you verify `api.host.com/my_route` exists and its not actually `host.com/my_route`?
<FromGitter>
<eliasjpr> Look at the remote address or one of the http headers such as referer or forwarded for
<FromGitter>
<eliasjpr> Those headers contain domain information for the request.
<FromGitter>
<damianham> @andrewc910 just out of interest and given the low cost of hosting amber projects why would you not create a new amber project for the subdomain if the routes are different and use nginx server definitions to proxy to the different amber instances ?
<FromGitter>
<andrewc910> @eliasjpr Thank you! I will give this a try. Much appreciated. ⏎ ⏎ @damianham Because I prefer monoliths. It's a stupid simple reason, I know. I don't enjoy spinning up server, configuring nginx, monitoring, etc. And i only want a subdomain for organizational reasons. No real technical reason. If i can get subdomains to work, cool, if not its not really a big deal. ⏎ ⏎ I think I am going to try and make