env file?

hi @jezdez, this may be completely out of scope as the project is literally named envdir, but I was wondering if its possible to provide a single file with all of the variables for each environment. so like:

prod
  - .env
dev
  - .env

this is mainly because I run programs both locally and with docker and docker allows me to specify a --env argument with a single file of environment variables. this way I can use the same file of environment variables for locally running a program and docker

thanks!

[AlJohri]

thanks @blueyed, that’s what I ended up doing

posting this here for the future:

The snippets below accomplished what I needed.

Load envs/local or .env into current shell:

if [ -d "envs/local" ]; then
    echo "sourcing envs/local directory..."
    for f in envs/local/*; do eval $(echo export $(basename $f)=$(cat $f)); done
elif [ -f ".env" ]; then
    echo "sourcing .env file..."
    export $(cat .env | grep -v "^#" | xargs)
fi

notes:

• replacing eval with echo in the for loop can help create a real env file if one likes. Sourcing it into the current shell worked well enough for me.
• this probably doesn’t work with multiline variables or maybe even variables with spaces or special characters. doesn’t apply for my usage right now
• this will choke on .DS_Store files and other random artifacts in the folder

docker-compose using external environment variables instead of an env-file file

version: '2'
services:
  myservice:
    environment:
      DATABASE_URL: ${DATABASE_URL}
      DEBUG: ${DEBUG}

https://docs.docker.com/compose/environment-variables/#/substituting-environment-variables-in-compose-files

usage if env variables are loaded in current shell: docker-compose up myservice usage using envdir: envdir envs/local docker-compose up myservice

[AlJohri]

haha thanks! that looks good, I’ll have to try that. not as great at the bashfu just yet 😃