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
On the host it would (still be) the responsibility of the user how to handle it - it's not baget's problem. But in the container, it would be mounted as a file and so cannot leak.
If the user is not using a docker swarm then docker secrets are not available, so in that case just let him use environment variables as usual (or he should run a single-node swarm, which is easy to do). That would be backwards compatible.
Thank you for considering it!
The text was updated successfully, but these errors were encountered:
Currently the API key is provided in an env file. That means it is exposed as an environment variable, as well as in logs.
Ideally it should be a docker secret.
On the host it would (still be) the responsibility of the user how to handle it - it's not baget's problem. But in the container, it would be mounted as a file and so cannot leak.
If the user is not using a docker swarm then docker secrets are not available, so in that case just let him use environment variables as usual (or he should run a single-node swarm, which is easy to do). That would be backwards compatible.
Thank you for considering it!
The text was updated successfully, but these errors were encountered: