3 ms·
This is not something a startup can change directly. If you are too purist you’ll never get traction. What they can do however, is push towards better options,
by klabb3 4y ago
This is not something a startup can change directly. If you are too purist you’ll never get traction. What they can do however, is push towards better options, publish or reuse an interoperable spec, and offer it on an opt-in with good dx.
- vmatsiiako 4y agoThank you! This is our plan indeed! Environment variables are still by far the most popular approach for storing secrets - and we are trying to create a better (more secure) alternative for managing environment variables and secrets than, let's say, .env files, and at the same time an easier alternative compared to other secrets managers. With time, we will be adding more niche and secure approaches mentioned in this thread to direct the developer community.
- Terretta 4y ago> Environment variables are still by far the most popular approach for storing secrets And `password` is still by far the most popular password. Why not just call it environment management, and warn ENV is not secret, so you don't spread the wrongness?
- 3np 4y agoplaint-text files (pick any of yaml/ini/toml/json/.env format) are all in a similar level of normal as env vars and can not be called niche, no?