3 ms·
The docs don’t make it very obvious how are the environment variables actually applied. And I think .env files are much easier to manage and share. `envelope ch
by Kwpolska 2y ago
The docs don’t make it very obvious how are the environment variables actually applied. And I think .env files are much easier to manage and share. `envelope check` could be replaced with a CURRENT_ENV environment variable in an .env file. I can’t see how it would help avoid environment confusion more than $CURRENT_ENV displayed in your prompt would. (Or even better, not having production credentials on developers’ machines…)
- mattrighetti 2y ago> The docs don’t make it very obvious how are the environment variables actually applied. Actually, they are not applied. This is a tool that helps you manage them, you can see it as a replacement of .env files. > `envelope check` could be replaced with a CURRENT_ENV environment variable in an .env file Can you elaborate more on this? I've never used that tbh and I'm interested
- Kwpolska 2y ago> Actually, they are not applied. This is a tool that helps you manage them, you can see it as a replacement of .env files. The point of .env files is for tools (shells or libraries like dotenv) to read the file and actually use them. How do you do that with your tool, considering it uses a custom format? > Can you elaborate more on this? I've never used that tbh and I'm interested There is nothing special, just define a variable in .env, and then either echo it manually, or change your shell prompt to apply it.