Every route ends the same way: get the values into .env files on your machine, push them with StoreEnv, check them, then delete the plain files you don't need.

From a plain .env#

.env becomes the default environment and .env.<name> files become environments named after the suffix.

$ cd my-app
$ storeenv init
$ storeenv push -m "Move to StoreEnv"

From dotenv-vault#

dotenv-vault's pull writes .env, and .env.production for the production environment. Check its documentation for your version's options.

$ npx dotenv-vault@latest pull
$ npx dotenv-vault@latest pull production
$ storeenv init && storeenv push -m "From dotenv-vault"

From Doppler#

Run it in the folder linked to your Doppler project (doppler setup). Check Doppler's documentation for your configs' names.

$ doppler secrets download --no-file --format env --config dev > .env
$ doppler secrets download --no-file --format env --config prd > .env.production
$ storeenv init && storeenv push -m "From Doppler"

From Infisical#

Run it in a folder initialised with infisical init. Check Infisical's documentation for your environments' slugs.

$ infisical export --env=dev --format=dotenv > .env
$ infisical export --env=prod --format=dotenv > .env.production
$ storeenv init && storeenv push -m "From Infisical"

After pushing#

• storeenv pull --stdout --env production to compare what StoreEnv holds.
• Invite your team (see Teams).
• Delete exported files you don't need, and keep .env files out of Git: storeenv scan warns when one is tracked or not ignored.