If your env file is a script that you source manually, I’d call it env.sh instead. Historically this has been my approach, but in production environments it’s

If your env file is a script that you source manually, I’d call it env.sh instead. Historically this has been my approach, but in production environments it’s convenient to have a static list of variables with no “export” instead since eg systemd’s EnvironmentFile only supports that.