Stop Putting Secrets in .env Files
jonmagic.com
Stop Putting Secrets in .env Files
1–10 of 21 posts
Re: Stop Putting Secrets in .env Files
#2So the solution is to use a proprietary password manager instead? No thanks
Re: Stop Putting Secrets in .env Files
#3So the solution is to use a proprietary password manager instead? No thanks
This is a MUCH better solution
https://wiki.archlinux.org/title/Systemd-creds
Re: Stop Putting Secrets in .env Files
#4You will probably really like https://varlock.dev
It’s a whole toolkit for this - with built in validation, type safety, and extra protection for sensitive secrets.
Re: Stop Putting Secrets in .env Files
#5People still code on their local boxes? op is not biometric secured over an ssh tunnel
Re: Stop Putting Secrets in .env Files
#6[deleted]
Re: Stop Putting Secrets in .env Files
#7Mfw typing the command stores the password in plaintext in my shell history
Re: Stop Putting Secrets in .env Files
#8It may be marked as Beta, but I've been using https://developer.1password.com/docs/environments/ since October-ish with no issues.
Re: Stop Putting Secrets in .env Files
#9Nice. One more benefit of this is when using LLM tools like Claude Code or Codex to do something and run tests on a worktree, this solution would work seamlessly.
Re: Stop Putting Secrets in .env Files
#10It may be marked as Beta, but I've been using https://developer.1password.com/docs/environments/ since October-ish with no issues.
I'm pretty sure this uses FIFO under the hood, that's a smart idea !