Phase - Open source application secrets management platform for developers
What we are building and how it works (TL;DR):
- CLI that replaces .env files by imports secrets, encrypting and syncing them to the backend. The CLI injects secrets into any application at runtime as environment variables.
- A frontend web app to CRUD key, value pairs across dev, staging, prod envs. Add teammates. View logs.
- An backend API to store secrets data. Sync them to common platforms like GitHub, Kubernetes, AWS etc.
Help needed: Contributors are welcome to try the platform and improve it by creating or picking up GitHub issues on any of the above repos, adding new integrations, features, and docs!
I don't think this is the best approach. I am building https://phase.dev which lets you import secrets (.env), encrypt secrets (end-to-end encrypted with keys you control), sync them to other services/platforms (think AWS, GitHub, Kubernetes), and inject them into applications at runtime (e.g., phase run node index.js).
In source maps, the mapping is done between the transformed code (like minified or bundled JavaScript) and the original source code. As long as the transformations are consistent and predictable, source maps remain effective. When you replace a unique placeholder with an actual value, you're essentially making a very targeted change that shouldn't alter the overall structure or flow of the code. This means the source maps should still accurately reflect the relationship between the source code and the transformed code, except for the parts where the placeholders were replaced.