docker compose: reading credentials from .env file

This seems to be the simplest way of handling credentials:

write actual credentials in a .env file
docker (compose) will automatically look for such a file to substitute ${variable-name} in docker(-compose) files
adding .env to .gitignore so that secrets cannot be accidentally shared.

Github encrypted secrets are something that is specific to github actions and as such mostly useful to us when we do CI.

But until then I can't think of a simpler way to substitute credentials. Is this alright for everyone?

riesgos / async