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
The frontend application configuration is defined in config.tsx - and the values are provided as environment variables at build time.
If we have a goal to provide a Docker image with the Argus frontend in it, this still needs to build everything from scratch at deployment time, since all the configuration is statically compiled into the resulting JavaScript files. This makes every deployment situation "fat" and time-consuming.
I think it's desirable for frontend deployments to be as lightweight as possible. Can we find ways to generate a static file with JavaScript or JSON-based configuration from the run-time environment, without involving the entire npm build framework, and have the React application load this file at runtime?
Surely this situation is not unique in the world - so it's likely someone else has made useful solutions we can learn fro.
The text was updated successfully, but these errors were encountered:
I would assume dotenv isn't much different from today's solution: It grabs variables from the environment as npm runs - this environment isn't available when the resulting JS code runs in the browser.
The frontend application configuration is defined in
config.tsx
- and the values are provided as environment variables at build time.If we have a goal to provide a Docker image with the Argus frontend in it, this still needs to build everything from scratch at deployment time, since all the configuration is statically compiled into the resulting JavaScript files. This makes every deployment situation "fat" and time-consuming.
I think it's desirable for frontend deployments to be as lightweight as possible. Can we find ways to generate a static file with JavaScript or JSON-based configuration from the run-time environment, without involving the entire npm build framework, and have the React application load this file at runtime?
Surely this situation is not unique in the world - so it's likely someone else has made useful solutions we can learn fro.
The text was updated successfully, but these errors were encountered: