Nah, just use direnv instead, comrade.
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.
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?
Environment variable abuse
Waiting for the leak announcements
Lmao, use Nix instead, or if that’s too complicated use DevBox.
Also, nobody with more than 0 brain cells will pay for this trash.
