4 ms·
Git-Popper: I Built a Tool to Securely Manage .env Files and Secrets Across Repo
- sim7c00 2y agoi dont really see how this is more secure alternative than adding sensitive files and types in gitignore, which you still have to do when using this. can you explain a little? maybe i am missing something here.. shared secrets imho should be on a vault like system. env files etc. are almost a crime in itself if they contain things like keys. maybe my views are not aligned with how a lot of devs work though :') that being said, i might consider it for 'additional use cases #2' which actually seems really useful (to me).