Introducing OnlyNv: Your one-stop solution for managing environment variables.
-
This post did not contain any content.
-
System shared this topic
-
This post did not contain any content.
Waiting for the leak announcements
-
This post did not contain any content.
Environment variable abuse
-
This post did not contain any content.
Oh wow.
That looks like an overly complicated solution to a problem that doesn't exist. Synching stuff that is in git? Why not just use.... git?
Also npm.... and the example has an env var named "DB_PASS" in it. You never put passwords in version control. -
This post did not contain any content.
Lmao, use Nix instead, or if that’s too complicated use DevBox.
-
This post did not contain any content.
The best way to manage environment variables: don't use environment variables.
-
The best way to manage environment variables: don't use environment variables.
What do you do instead for dynamic values that are needed at runtime and inappropriate to check in to version control?
-
Oh wow.
That looks like an overly complicated solution to a problem that doesn't exist. Synching stuff that is in git? Why not just use.... git?
Also npm.... and the example has an env var named "DB_PASS" in it. You never put passwords in version control.It is generally considered a bad idea to use envs for passing secrets in general since envs for process n are available to other processes which have access and permission.
