Written by Mot
Push .env securely to dotenv-vault.
$ npx dotenv-vault push
remote: Securely pushing (.env)... done
remote: Securely pushed development (.env)
That's it!
For more information on the push command, run dotenv-vault help push.
$ npx dotenv-vault help push
Push .env securely
USAGE
$ dotenv-vault push [ENVIRONMENT] [FILENAME] [-m ] [-y]
ARGUMENTS
ENVIRONMENT Set environment to push to. Defaults to development
FILENAME Set input filename. Defaults to .env
FLAGS
-m, --dotenvMe= Pass .env.me (DOTENV_ME) credential directly (rather than reading from .env.me file)
-y, --yes Automatic yes to prompts. Assume yes to all prompts and run non-interactively.
DESCRIPTION
Push .env securely
EXAMPLES
$ dotenv-vault push
[ENVIRONMENT]
Set environment to push to. Defaults to development
$ npx dotenv-vault push production
remote: Securely pushing production (.env.production)... done
remote: Securely pushed production (.env.production)
[FILENAME]
Set input filename. Defaults to .env for development. Otherwise defaults to .env.[ENVIRONMENT]
$ npx dotenv-vault push production .env.production
remote: Securely pushing production (.env.production)... done
remote: Securely pushed production (.env.production)
-m, --dotenvMe
Pass .env.me (DOTENV_ME) credential directly (rather than reading from .env.me file)
$ npx dotenv-vault push --dotenvMe=me_b1831e…
# use credential set from dotenvMe rather than .env.me file
-y, --yes
Automatic yes to prompts. Assume yes to all prompts and run non-interactively.
$ npx dotenv-vault push -y
# skips over prompt for permission to open browser window
Next command(s).
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 |
|