Env variables when programmatically loading template

[barrysteyn]

@Pavel910 mentions in the README that when loading a template programmatically, one can associate it with any .env:

That way you can deploy unlimited environments, add pre/post processing, load whatever .env you need, etc.

How would "whatever .env you need" be loaded? The only way I can think of loading env variables is to set it in process.env. This does not seem correct, is there a better way of doing things? If so, can the README be updated.

[Pavel910]

Since components do not have a built-in concept of stages or environments, you can handle your --env argument and load an appropriate env config file using, for example, env-cmd.

No time for PR, sorry,