Deal with environments in env:encrypt and env:decrypt

[foertel]

Hey,

I am preparing a PR for this but just wanted to get some input in the meantime. Environment handling is pretty inconsistent in env:encrypt and env:decrypt, right?

When I am in APP_ENV=test, env:decrypt will decrypt .env.test.encrypted to .env. If I specify --env=test, it will decrypt .env.test.encrypted to .env.test. There is no way to decrypt .env.encrypted as long as I am inside of an APP_ENV=test because --env is not checked for an empty value.

Along the same lines I can not encrypt .env as long as I am in APP_ENV=test.

Did I get this right so far?

My suggestion:

• use APP_ENV consistently so don't cross-decrypt .env.${APP_ENV}.encypted to .env
• allow --env= to be set empty and en-/decrypt .env to/from .env.encrypted when running in an APP_ENV=