Written by Mot
The .env.vault file uniquely identifies your project in dotenv-vault. You SHOULD commit this file to source control. It is safe to do so. Aside: DON'T commit your .env or .env.me to source control.
You can think of it like a unique git url at GitHub. It identifies your project so that your teammates pull the correct .env file from dotenv-vault.
Here's an example of what a .env.vault file looks like:
DOTENV_VAULT=vlt_9a165d…
The first thing you might notice is the formatting is the same as a .env file. This is intentional to allow for maximum future interoperability.
The DOTENV_VAULT key is important. It is required. It is that value that identifies your project uniquely to the dotenv vaulting mechanisms.
You can generate a .env.vault file at ui.dotenv.org or through dotenv-vault. The process is similar to creating and cloning your very first git repo on GitHub.
Learn more about dotenv-vault security.
Security Overview | |
.env file | |
.env.vault identifier | |
.env.me credential | |
How dotenv-vault works |
dotenv-vault new | |
dotenv-vault login | |
dotenv-vault logout | |
dotenv-vault open | |
dotenv-vault push | |
dotenv-vault pull | |
dotenv-vault versions | |
dotenv-vault whoami | |
dotenv-vault status | |
dotenv-vault help |
Use dotenv with Express |
|
Use dotenv and dotenv-vault with Express |
|