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 would like to to include a remix app alongside an existing legacy application by adding it to a sub-path. In this instance it would take over a section of our administration tool set. https://our-web-app.com/admin/preferred-gift <-- remix / path
I attempted a direct proxy-pass with nginx however as the expected relative paths were to https://our-web-app.com/build instead of https://our-web-app.com/admin/preferred-gift/build I ran into some issues.
If remix could accept a baseName such as /admin/preferred-gift and use that for routing and relative path resolution it would help.
There might also be a super simple solution that I am not seeing
The text was updated successfully, but these errors were encountered:
williamtstanley
changed the title
Integration within existing applications: basename
sub-path support with baseNameApr 29, 2021
williamtstanley
changed the title
sub-path support with baseName
sub-path support with baseName
Apr 29, 2021
I would like to to include a remix app alongside an existing legacy application by adding it to a sub-path. In this instance it would take over a section of our administration tool set. https://our-web-app.com/admin/preferred-gift <-- remix
/
pathI attempted a direct proxy-pass with nginx however as the expected relative paths were to
https://our-web-app.com/build
instead ofhttps://our-web-app.com/admin/preferred-gift/build
I ran into some issues.If remix could accept a baseName such as
/admin/preferred-gift
and use that for routing and relative path resolution it would help.There might also be a super simple solution that I am not seeing
The text was updated successfully, but these errors were encountered: