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
As mentioned in the readme, it's not a great idea to use passwords, OTP, etc., in plain text.
One solution is to use a 'hidden' .secrets.env file, which comprises a list of all your emails, passwords, keys, etc., entered as 'VALUE=actual`, for example:
Then, in the compose.yaml, you can add the following line, making sure to specify the actual path:
env_file:
- /path/to/fgc/.secrets.env
When using docker compose up -d it should build and run the container as if you'd entered all your emails/passwords/keys as environmental variables, but pulls them from the hidden 'dot' file. I'm not sure how to do this a docker run command, or if there's other/better solutions, but this one works for me and is relative easy to implement.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
Thanks for this clever bot!
As mentioned in the readme, it's not a great idea to use passwords, OTP, etc., in plain text.
One solution is to use a 'hidden' .secrets.env file, which comprises a list of all your emails, passwords, keys, etc., entered as 'VALUE=actual`, for example:
etc.
Then, in the compose.yaml, you can add the following line, making sure to specify the actual path:
When using
docker compose up -d
it should build and run the container as if you'd entered all your emails/passwords/keys as environmental variables, but pulls them from the hidden 'dot' file. I'm not sure how to do this a docker run command, or if there's other/better solutions, but this one works for me and is relative easy to implement.Beta Was this translation helpful? Give feedback.
All reactions