Use VAPOR_ENV for non-standard environment option

[joelvh]

Vapor lets you set up multiple environments, each with its own name. While they are different environments, they may all still run in "production mode" with APP_ENV=production. But the encrypted environment variables each Vapor environment needs will be different.

The issue is that the naming convention of .env.production.encrypted in the root of the repository does not allow for storing encrypted environment variables for multiple Vapor environments that run in production mode.

This PR introduces VAPOR_ENV to mirror the environment name used for each Vapor environment. (In our case, we use dev, demo and production -- sometimes staging.) FWIW we use STAGE as the environment variable to distinguish environments, but VAPOR_ENV would be less opinionated.

[joedixon]

Thanks, I think this looks like a good solution.

[joelvh]

Thanks @joedixon!

Is there a way to reference the Vapor environment name currently, that might populate this automatically? Or maybe set the preference for Vapor vs. Laravel environment name to be used?

Either way, this solution works for us!

[joedixon]

@joelvh the only place we populate Vapor's environment name is in APP_ENV, but if you override that, it's not available any longer, so I think this is a good option.

[joelvh]

Ah, that's great to know! Didn't realize that's where it is set by default. I'm happy to update the docs if you can point me to them.