We've all been there, sharing .env files in Slack to get a Javascript application quickly working on someone's local machine while feeling bad about s

Search code, repositories, users, issues, pull requests...

submited by

Style Pass

2025-01-05 05:30:04

We've all been there, sharing .env files in Slack to get a Javascript application quickly working on someone's local machine while feeling bad about security practices. 🫠

But teams always have a shared secret or password manager (1Password, Bitwarden, Google Secrets Manager, AWS Secrets Manager, etc)...

What if you just had a nice little JSON file in your code repository that defined which environment variables to fetch from any manager?

salakala does exactly that! It wraps around your secrets manager and generates .env files from the secrets you define in your salakala.json file. As long as you're logged in to the manager you're using, it should just work.

salakala is fresh and under development! Please report any issues you find. If you want to add support for a new provider, please open an issue or a PR.

You can use environment variables in your secret paths using ${VARIABLE_NAME} syntax. This is useful when you need to dynamically configure parts of the secret path: