#Relative basepath
6 messages · Page 1 of 1 (latest)
relative to the root of the app we host all of our apps at work behind a reverse proxy https://domain.company.com/my-app sometimes we deploy the same app under a different name on the same domain. To beta things for example. I was just wondering if there was an easy way to not have to update the basepath on the router every time we wanted to deploy under a different app name.
still dont understand the setup. what would be variants of the basepath that could occur?
so the main instance could be something like https://domain.company.com/my-app then another instance could be https://domain.com/my-app-variant1. Our apps are all deployed as docker containers using ECS in amazon so we either have to change the basepath for every build. It would nice if the basepath for the router could be something like ./ so that router could infer the base from the URL. so for the two instances the base would end up as /my-app and the second would. /my-app-variant1
I may not be explaining this well.