Replies: 2 comments
-
I wanted to share our use case as well. For convenience, we put our assets into a docker container with nginx serving the files. However, we need to deploy this to different hostnames, potentially on different paths. It doesn't seem possible, playing with the We want to achieve:
Would love any suggestions about how to manage this at runtime. For the time being, we have done a workaround for the path modelled off of this guide, while other runtime variables are handled based on |
Beta Was this translation helpful? Give feedback.
-
+1
|
Beta Was this translation helpful? Give feedback.
-
We are using vite to build our react app.
One of the needs in our project is to be able to build the assets once, run/serve the app as a single instance, however support multiple base paths at runtime (e.g: https:///it, https:///fr, https:///app/de etc.).
I have looked at the renderBuiltUrl option of the experimental config, but was not sure how to adapt that to multiple base paths and that too at runtime.
Is there any way to achieve what I am looking at?
Beta Was this translation helpful? Give feedback.
All reactions