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
We have encountered a problem where it is currently not possible to pass environment variables to a Docker container from outside. This seems to be due to the way the variables are integrated.
It would be much nicer if we could pass the variables through a separate environment file, such as a config.json.
Then, we could refer to the config.json when running npm serve, and in the Docker context, an environment variable or an env-file could be passed.
This would mean that no variables are required at build time.
Also, this approach would eliminate the need to constantly rebuild the container or run npm install, and it would be possible to provide one's own access token or other Vue variables at container start, without them being stored in the container during the build.
However, this would require adjusting how the variables are processed.
Thanks
The text was updated successfully, but these errors were encountered:
So, is it possible to change the app to stateless applicaton so that all the information in .env are added during runtime?
I used to create a similar application with python flask, will try it with copilot :-)
Hi,
We have encountered a problem where it is currently not possible to pass environment variables to a Docker container from outside. This seems to be due to the way the variables are integrated.
It would be much nicer if we could pass the variables through a separate environment file, such as a config.json.
Then, we could refer to the config.json when running npm serve, and in the Docker context, an environment variable or an env-file could be passed.
This would mean that no variables are required at build time.
Also, this approach would eliminate the need to constantly rebuild the container or run npm install, and it would be possible to provide one's own access token or other Vue variables at container start, without them being stored in the container during the build.
However, this would require adjusting how the variables are processed.
Thanks
The text was updated successfully, but these errors were encountered: