> but how are the environmental variables transferring from the production machines to where the tests are being run? tmux[1] is a terminal multiplexer, a scre

> but how are the environmental variables transferring from the production machines to where the tests are being run? tmux[1] is a terminal multiplexer, a screen alternative. Some speculation, they might have stared the session on a remote machine; set `DATABASE_URL`; use it for something; detach from the session; to later reattached with the bash env still in tack; without the developer being aware he executed the tests commands. Another tmux "problem" is developers using it to tail logs with a infinite back-scroll to only fill up server memory. One solution was to kill all tmux session nightly via cron. Might have helped here. Finally as tui lover, try tmux! Really keeps the frustration at bay if you ssh to a box and your session drop to know your terminal workspace is still in tack. - https://github.com/tmux/tmux/wiki https://github.com/tmux/tmux/wiki