diff --git a/README.md b/README.md index 47c46fac..de564ea7 100644 --- a/README.md +++ b/README.md @@ -231,10 +231,12 @@ $ git push heroku main # heroku example That's it! On deploy, your `.env.vault` file will be decrypted and its secrets injected as environment variables – just in time. -See GitHub dotenv-vault README for more details. +

See GitHub dotenv-vault README for more details.

ℹī¸ **A note from Mot**: Until recently, we did not have an opinion on how and where to store your secrets in production. We now strongly recommend generating a `.env.vault` file. It's the best way to prevent your secrets from being scattered across multiple servers and cloud providers – protecting you from breaches like the [CircleCI breach](https://techcrunch.com/2023/01/05/circleci-breach/). Also it unlocks interoperability WITHOUT native third-party integrations. Third-party integrations are [increasingly risky](https://coderpad.io/blog/development/heroku-github-breach/) to our industry. They may be the 'du jour' of today, but we imagine a better future with `.env.vault` files. +The above example, for brevity's sake, used the 🔐 Vault Managed solution to generate your `.env.vault` file, but you can also use the đŸ’ģ Locally Managed solution. [Read more here](https://github.com/dotenv-org/dotenv-vault#how-do-i-use--locally-managed-dotenv-vault). Our vision is that other platforms and orchestration tools adopt the `.env.vault` standard as they did the `.env` standard. We don't expect to be the only one providing a service around `.env.vault` files. + ## 🌴 Manage Multiple Environments You have two options for managing multiple environments - locally managed or vault managed - both use dotenv-vault.