Dotenv VS Doppler

Dotenv Reviews

1. Connor    

   over 1 year ago

   Dotenv makes working with .env files across a team and multiple environments a great experience. Very simple and easy to set up and easy to work with

   👍 Pros:    Easy to use|Quick response time from developers|Sync across all my devices|Great user experience|Convenience

   👎 Cons:    None so far
2. Sahil    

   over 1 year ago
   Awesome to manage environment variables

   Works smoothly without any issues and syncs env variables across different environments.

   👍 Pros:    Easy to use|Easy integration|Quick and easy|Quick response time from developers

   👎 Cons:    None that i can think of

Doppler Reviews

Dotenv mentions (1)

• free-for.dev

  Dotenv — Sync your .env files, quickly & securely. Stop sharing your .env files over insecure channels like Slack and email, and never lose an important .env file again. Free for up to 3 teammates. - Source: dev.to / over 1 year ago

Doppler mentions (19)

• Keeping secrets out of public repositories

  If you’re asking yourself where you should be keeping secrets, you should be using a secrets manager. Two examples include Doppler (https://doppler.com). - Source: Hacker News / 2 months ago

• Ask HN: How do you get developers to trust your product?

  I'm a developer advocate at Doppler (https://doppler.com), and we are a secrets (API keys, certs, etc.) management platform. I create content that's aimed at informing readers about our product. One of the biggest challenges I've encountered is convincing developers to trust our platform in a world of zero trust. Since we store important and sensitive data, we are often asked about how we encrypt data and what we... - Source: Hacker News / 2 months ago

• Ask HN: Where do you save your API keys?

  Doppler (https://doppler.com) is my preferred tool for storing API keys. It centralizes where you manage all of your environmental variables and makes it so you never risk exposing your API keys in a code repo. There's a CLI tool that makes it easy to use all of your environment variables while you're developing and a ton of integrations for wherever you prefer to deploy your... - Source: Hacker News / 3 months ago

• A mistakenly published password exposed Mercedes-Benz source code

  It seems like they made a lot of assumptions that something like this wouldn't happen. They assumed employees would never leak secret information, and that their GitHub repos would never be exposed. They could've used https://doppler.com) and never had this problem. It's a little too easy to get comfortable thinking things work well the way they are. This should be a warning to other companies to seriously... - Source: Hacker News / 3 months ago

• A mistakenly published password exposed Mercedes-Benz source code

  It's absolutely nuts that a company like Mercedes-Benz isn't using some type of secrets manager (like https://doppler.com or AWS Secrets Manager) to restrict access to this type of data. It also seems like they have extremely bad practices if they're pushing passwords and keys to code repos. - Source: Hacker News / 3 months ago