Support for custom .env files? #220
Description
Is it possible to specify .env files with custom names, and/or multiple .env files? This would be useful to provide a .env file (which is kept under version control) containing default settings while giving the user the ability to customise some values using their own .env.local file.
Example invocations:
# Start processes with default settings (read from .env file and
# any environments defined inside `process-compose.yaml`)
$ process-compose up
# Use only the alternative settings in `.env.local`
$ process-compose -e .env.local up
# Use default settings in `.env` except for any customised values in `.env.local`
$ process-compose -e .env -e .env.local upMany thanks!