Subdomain as Route

[ruby pebble]

Hey guys, sorry this is a bit of a weird one,

Im wondering if i am able to route a wildcard subdomain to a route in remix.. IE

subdomain.example.com = example.com/subdomain

But the user sees it as subdomain.example.com

and then going further into the urls... IE Settings page...

they would see subdomain.example.com/settings

(instead of the example.com/subdomain/settings)

[sinful jetty]

The router doesn’t have anything to define subdomains, you would have to check the request.url to get the origin of the url (domain) and verify the subdomain yourself

[tribal mist]

you will need to handle this replacement before the request gets handled by remix. This depends on what stack/hosting provider you are using. Basically you'll change the request.url from subdomain.mydomain.com/path to mydomain.com/subdomain/path before passing it to createRequestHandler. I did this using aws lambda successfully, but not sure how it would work in an express-style host.

[ruby pebble]

im using blues stack via Fly.io .. This is exactly what im trying to achieve!

[sinful jetty]

I would check the hostname from the request.url instead of trying to hack Remix to believe that subdomain.example.com/settings is a request to example.com/subdomain/settings and also ensure that keeps working correctly on client-side navigations

you could have a function like this

function getSubdomain(request: Request) {
  let { hostname } = new URL(request.url);
  let [subdomain] = hostname.split(".")
  return subdomain
}

and use it in every loader to know the subdomain of the request.url

[tribal mist]

well if you want to basically make remix treat it as a path name, (ie to use as a param) you need to modify it pre-remix

[sinful jetty]

it will not work client-side

because client-side the route will expect the subdomain to be part of the pathname

[ruby pebble]

hmm.. would i be better off creating 2 apps..

one for splash page registration .. and the second for the client's app..

im trying to kinda clone what shopify does with there accounts.. where when you register you get assigned a domain name... and then the users of that domain name can have sub users with limited access...

essentially just smoke screening the url lol kind of like how when you create a shopify account... your login page is yourdomain.myshopify.com

[ruby pebble]

and are you suggesting that after the subdomain check it redirects to example.com/Subdomain/settings instead of trying to keep it on that subdomain?

[sinful jetty]

Keep the user on the same url, just check the subdomain using that function which would then work as a a value to know what data to show

[ruby pebble]

ahhh.. so maybe i should change my route folder to have a /app instead of domainId.. so that they dont see the long url path!

And then on index.. i can create a check for subdomain and if it exsists redirect to /app

[turbid vector]

I do an initial check on the root for subdomain styling if any. And then use a similar function for each loader/action to check for things like auth, etc

[ruby pebble]

Yeah i think thats a great idea.

I think im going to create the user dashboard under /app route and do the checks for the subdomain too...

[turbid vector]

That is essentially how we do it 🙂

[ruby pebble]

ayeeeeee!! now to get subdomains on my dev env lol!!

[turbid vector]

Update your hosts - on Mac they are typically under /etc/hosts

[turbid vector]

You’ll do something like 127.0.0.1 subdomain.mydomain.com

You’ll still need to add your port in the browser when accessing

On dev