.env vs compose patterns

[ethanknox-palmetto]

I think a docker-compose bug may have made our code better.

We were relying on a pattern with .env and .env.template that in hindsight seems grody. Let's make the defacto be that we define envars in compose (or in the command processes themselves if needed) and only populate called-for envars in .env. That is much cleaner and less cryptic (when you get a repo with no .env and need to create one you shouldn't have to guess at the keys) .

[ethanknox-palmetto]

relates to #27