Environment variables don't appear to be getting picked up

[satsie]

Here's a nice vague issue. @benalleng and I have noticed the server doesn't seem to be picking up environment variables. After a fresh deployment, many of them operate off hardcoded defaults.

For example, we had to set CONTAINER_TERMINATION_SCHEDULE in the .env (maybe that was a one time step?). When I was on the server recently I got nothing when I ran echo $MAX_SCRIPT_EXECUTION_TIME

Further investigation is needed to figure out if it's an issue where we aren't setting the env vars, or if there's an bug in the logic when environment variables are read.

[benalleng]

I suspect this is some sort of CI issue as I have set these vars in the past but I think they get overridden on every new push to master