3 ms·
We use Bitwarden[0] for our secrets. It's open-source with a hosted option. Makes sharing passwords and keys across the team pretty straightforward. In additio
by gingerlime 6y ago
We use Bitwarden[0] for our secrets. It's open-source with a hosted option. Makes sharing passwords and keys across the team pretty straightforward.
In addition to it, we use envwarden[1], which is a simple open-source wrapper around the Bitwarden CLI to manage our server secrets. It's super simple, but does the job for us well. We can then manage both passwords and keys in one place.
Disclaimer: I created envwarden. I'm not affiliated with Bitwarden in any way however. Just a happy customer.
[0] https://bitwarden.com/ https://bitwarden.com/
[1] https://github.com/envwarden/envwarden https://github.com/envwarden/envwarden
- shekhardesigner 6y agoI didn't know about envwarden till you mentioned it here. We migrated from bitwarden to offline client machine for the reason that we didn't wanted a copy of our encryption key be available anywhere else online.
- lux 6y agoenvwarden looks awesome! Is there any potential for the Bitwarden project to incorporate it/make it officially supported?