Show HN: Keynest – a simple offline secrets manager (github.com)

I tend to build a lot of small tools, side projects and experimenting with many different technologies and always run into the same issues:

- secrets are in .env files which i need to copy around between the projects - hardcoded secrets in code which i forget to delete when commiting - keep track of set environment variables in different environments

and i tried different solutions out there (1Password, Vault, ..) but it felt like too heavy for my local projects.

This is why i built Keynest for my personal local workflow. I use it currently for small local experimenting stuff only.

It is basically one encrypted file on my disk and i decide what secrets i want to inject while running commands: E.g. keynest exec -- docker compose up

Curious if others have the same pain with local secrets or if I'm overengineering this.

Would love some feedback.