We did something like this. We injected the variables with a script in the container. We contemplated building a /config endpoint that would expose those varia

We did something like this. We injected the variables with a script in the container. We contemplated building a /config endpoint that would expose those variables as a way to make it more stable, as string replacement is inherently brittle. However, due to some legacy systems out there the website wasn't always hosted at the root of the domain. It could be hosted at www.example.com/subfolder/. This broke the SPA setup (think HTML5 navigation mode). So for the html base we still had to do string injection / replacement.