You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2020. It is now read-only.
I've searched through the current codebase but do not see any support for registering routes based off of a subdomain as I have a requirement for this and cannot run multiple servers.
For example:
api.service.com/ => api/index.js
Is this on the roadmap or should [I / a contributor] go ahead and work on this functionality?
The text was updated successfully, but these errors were encountered:
@andrewapperley sorry for the delay in reply. This isn't currently on the roadmap, so any help you'd be able to offer would be much appreciated. Curious on your thoughts as to how to approach this.
Hey @totherik don't worry about it, I pulled the issue because I was coming to the conclusion that subdomain handling is more appropriate as a middleware on every request and not to be handled at the route creation level. However it should be possible but I haven't nailed down how to do it quite yet. Checking every request if its coming from a subdomain is hacky in my opinion (how a few middleware projects handle this so far). I'll comment back when I've given this some more time but my first thoughts are to add a second option in the config for another folder that would house the controllers or change how directory.js searches for controllers.
I've searched through the current codebase but do not see any support for registering routes based off of a subdomain as I have a requirement for this and cannot run multiple servers.
For example:
Is this on the roadmap or should [I / a contributor] go ahead and work on this functionality?
The text was updated successfully, but these errors were encountered: