Frontend Configuration Mechanisms about frontend HOT 5 CLOSED

Yes, you now need to mount your config into the backend container( as /home/node/app/dist/src/config/frontend.config.json), the frontend now just needs the API url.

from frontend.

But that means that everyone has to mount in both places, frontend to get the api url and backend to get the file?

from frontend.

Actually no, the initial URL is hardcoded and assumes that FE and BE are serverd on the same domain.

This also means you could in theory server different backends with a singel FE deployment(using hostname based routing).

from frontend.

The fallback is there (only) for proxyless dev setups, where the BE is serverd on a different port. Then you need to serve the config on the FE.

from frontend.

Relooking at this old issue. Is it tru that the only reason to support frontend configuration in the front end at all now is if your api url were non-standard, in which case you'd have to put in the config.json in the front end to pick it up.

from frontend.