How should we manage multiple env files?

[pbchase]

@ljwoodley asked this week:

Should a env_files folder or similar be created for the secondary envs with email addresses?

[pbchase]

I have felt the need for this as well. It's not unusual for us to overload a docker run command with multiple environment files in series of --env-file foo.env parameters. This is almost always done to change email addresses when they are not data-driven. These are project-specific configuration data, but they are not secrets. As such, I don't see a problem committing these to a private, project-specific git repository.

Related to this, we have some older code in the build.sh that references the site concept to copy env files. We sunsetted that concept, but we didn't destroy the code. That code is copying the contents of a folder named env to a folder on the deployed host. That could meet the need to manage a suite of configuration files (sans secrets, of course) that need to be deployed.

Looping in @ChemiKyle

[ChemiKyle]

We discussed this, I support the idea of git tracking env files in rcc.* repos as long they don't contain secrets.