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
I want to install the expose server on my root domain, but I don't want expose routes to clash with my own web application.
I know that expose have 3 separates routes:
expose.< domain > the web management interface
*.< domain > the dynamic subdomains
but it seems there are some routes (at least one: /expose/control) that reside on the root domain.
Question:
Is it the only route (/expose/control) ?
It seems it's hardcoded, (cannot place in a subfolder). It's normal ?
I know /expose/control get's called from expose client when doing "expose share"
I setup an nginx proxy for /expose to proxy-it to the expose process listening no a local port and it "seems" to work, but I want to make sure that I am catching all routes AND that the catched routes won't change and clash with my app in the future.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I want to install the expose server on my root domain, but I don't want expose routes to clash with my own web application.
I know that expose have 3 separates routes:
expose.< domain > the web management interface
*.< domain > the dynamic subdomains
but it seems there are some routes (at least one: /expose/control) that reside on the root domain.
Question:
I know /expose/control get's called from expose client when doing "expose share"
I setup an nginx proxy for /expose to proxy-it to the expose process listening no a local port and it "seems" to work, but I want to make sure that I am catching all routes AND that the catched routes won't change and clash with my app in the future.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions