Add --env-file parameter
This helps keeps Up more in line with Apex and allows trickier workflows. http://apex.run/#environment-variables
Possibly! But probably only on Pro since it has the extra env var stuff as well. Running into cases where up env ... isn't enough?
I use both apex and up in my project and it's just a bit annoying to have two different ways to dealing with env specs. I'm not using pro so currently I'm relying on switching env using apex --env-file flag and with UP I'm swapping up.conf(s). I feel that it just makes sense to unify the approach here by adding env-file support to up.
Yeah there's definitely that, if I end up doing an Apex 2.0 I think it'll be more like Up in terms of general UX but I don't see any harm in having multiple techniques to define env vars. I can't do too much for non-pro users though otherwise I can't even justify working on the project haha.