@dotenvx/next-env 1.74.2 → 1.74.3

package/node_modules/@dotenvx/dotenvx/README.md

@@ -0,0 +1,2781 @@
+[![dotenvx](https://dotenvx.com/banner.png?v2)](https://dotenvx.com)
+
+*a secure dotenv*–from the creator of [`dotenv`](https://github.com/motdotla/dotenv).
+
+* run anywhere (cross-platform)
+* multi-environment
+* encrypted envs
+
+[Read the whitepaper](https://dotenvx.com/dotenvx.pdf?v=README)
+
+ 
+
+
+### Quickstart [![npm version](https://img.shields.io/npm/v/@dotenvx/dotenvx.svg)](https://www.npmjs.com/package/@dotenvx/dotenvx) [![downloads](https://img.shields.io/npm/dw/@dotenvx/dotenvx)](https://www.npmjs.com/package/@dotenvx/dotenvx)
+
+Install and use it in code just like `dotenv`.
+
+```sh
+npm install @dotenvx/dotenvx --save
+```
+```js
+// index.js
+require('@dotenvx/dotenvx').config()
+// or import '@dotenvx/dotenvx/config' // for esm
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+ 
+
+or install globally - *unlocks dotenv for any language, framework, or platform!*
+
+<details><summary>with npm 🌍</summary><br>
+
+```sh
+npm i -g @dotenvx/dotenvx
+dotenvx encrypt
+```
+
+[![npm installs](https://img.shields.io/npm/dt/@dotenvx/dotenvx)](https://npmjs.com/@dotenvx/dotenvx)
+
+&nbsp;
+
+</details>
+<details><summary>with curl 🌐</summary><br>
+
+```sh
+curl -sfS https://dotenvx.sh | sh
+dotenvx encrypt
+```
+
+[![curl installs](https://img.shields.io/endpoint?url=https://dotenvx.sh/stats/curl&label=curl%20installs)](https://github.com/dotenvx/dotenvx.sh/blob/main/install.sh)
+
+&nbsp;
+
+</details>
+
+<details><summary>with brew 🍺</summary><br>
+
+```sh
+brew install dotenvx/brew/dotenvx
+dotenvx encrypt
+```
+
+[![brew installs](https://img.shields.io/github/downloads/dotenvx/dotenvx/total?label=brew%20installs)](https://github.com/dotenvx/homebrew-brew/blob/main/Formula/dotenvx.rb)
+
+&nbsp;
+
+</details>
+
+<details><summary>with docker 🐳</summary><br>
+
+```sh
+docker run -it --rm -v $(pwd):/app dotenv/dotenvx encrypt
+```
+
+[![docker pulls](https://img.shields.io/docker/pulls/dotenv/dotenvx)](https://hub.docker.com/r/dotenv/dotenvx)
+
+&nbsp;
+
+</details>
+
+<details><summary>with github releases 🐙</summary><br>
+
+```sh
+curl -L -o dotenvx.tar.gz "https://github.com/dotenvx/dotenvx/releases/latest/download/dotenvx-$(uname -s)-$(uname -m).tar.gz"
+tar -xzf dotenvx.tar.gz
+./dotenvx encrypt
+```
+
+[![github releases](https://img.shields.io/github/downloads/dotenvx/dotenvx/total)](https://github.com/dotenvx/dotenvx/releases)
+
+&nbsp;
+
+</details>
+
+
+<details><summary>or windows 🪟</summary><br>
+
+```sh
+winget install dotenvx
+dotenvx encrypt
+```
+
+</details>
+
+&nbsp;
+
+## Run Anywhere
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ node index.js
+Hello undefined # without dotenvx
+
+$ dotenvx run -- node index.js
+Hello Dotenvx # with dotenvx
+> :-D
+```
+
+see [extended quickstart guide](https://dotenvx.com/docs/quickstart)
+
+More examples
+
+<details><summary>TypeScript 📘</summary><br>
+
+```json
+// package.json
+{
+  "type": "module",
+  "dependencies": {
+    "chalk": "^5.3.0"
+  }
+}
+```
+
+```js
+// index.ts
+import chalk from 'chalk'
+console.log(chalk.blue(`Hello ${process.env.HELLO}`))
+```
+
+```sh
+$ npm install
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx run -- npx tsx index.ts
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Cloudflare Workers ⛅️</summary><br>
+
+```sh
+$ dotenvx encrypt -f .env.txt
+```
+
+```js
+// src/index.js
+import envSrc from '../.env.txt'
+import dotenvx from '@dotenvx/dotenvx'
+
+const config = dotenvx.config({ envs: [{ type: 'env', value: envSrc, privateKeyName: 'DOTENV_PRIVATE_KEY' }] })
+const envx = config.parsed
+
+export default {
+  async fetch(request, env, ctx) {
+    return new Response(`Hello ${envx.HELLO}`)
+  }
+}
+```
+```json
+"scripts": {
+  "deploy": "wrangler deploy",
+  "dev": "wrangler dev --var $(dotenvx keypair -f .env.txt --format=colon)",
+  "start": "wrangler dev --var $(dotenvx keypair -f .env.txt --format=colon)",
+}
+```
+
+</details>
+<details><summary>Deno 🦕</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "console.log('Hello ' + Deno.env.get('HELLO'))" > index.ts
+
+$ deno run --allow-env index.ts
+Hello undefined
+
+$ dotenvx run -- deno run --allow-env index.ts
+Hello Dotenvx
+```
+
+> [!WARNING]
+> Some of you are attempting to use the npm module directly with `deno run`. Don't, because deno currently has incomplete support for these encryption ciphers.
+>
+> ```
+> $ deno run -A npm:@dotenvx/dotenvx encrypt
+> Unknown cipher
+> ```
+> 
+> Instead, use `dotenvx` as designed, by installing the cli as a binary - via curl, brew, etc.
+
+</details>
+<details><summary>Bun 🥟</summary><br>
+
+```sh
+$ echo "HELLO=Test" > .env.test
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ bun index.js
+Hello undefined
+
+$ dotenvx run -f .env.test -- bun index.js
+Hello Test
+```
+
+</details>
+<details><summary>Python 🐍</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'import os;print("Hello " + os.getenv("HELLO", ""))' > index.py
+
+$ dotenvx run -- python3 index.py
+Hello Dotenvx
+```
+
+see [extended python guide](https://dotenvx.com/docs/quickstart)
+
+</details>
+<details><summary>PHP 🐘</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo '<?php echo "Hello {$_SERVER["HELLO"]}\n";' > index.php
+
+$ dotenvx run -- php index.php
+Hello Dotenvx
+```
+
+see [extended php guide](https://dotenvx.com/docs/quickstart)
+
+</details>
+<details><summary>Ruby 💎</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'puts "Hello #{ENV["HELLO"]}"' > index.rb
+
+$ dotenvx run -- ruby index.rb
+Hello Dotenvx
+```
+
+see [extended ruby guide](https://dotenvx.com/docs/quickstart)
+
+</details>
+<details><summary>Go 🐹</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'package main; import ("fmt"; "os"); func main() { fmt.Printf("Hello %s\n", os.Getenv("HELLO")) }' > main.go
+
+$ dotenvx run -- go run main.go
+Hello Dotenvx
+```
+
+see [extended go guide](https://dotenvx.com/docs/quickstart)
+
+</details>
+<details><summary>Rust 🦀</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'fn main() {let hello = std::env::var("HELLO").unwrap_or("".to_string());println!("Hello {hello}");}' > src/main.rs
+
+$ dotenvx run -- cargo run
+Hello Dotenvx
+```
+
+see [extended rust guide](https://dotenvx.com/docs/quickstart)
+
+</details>
+<details><summary>Java ☕️</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'public class Index { public static void main(String[] args) { System.out.println("Hello " + System.getenv("HELLO")); } }' > index.java
+
+$ dotenvx run -- java index.java
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Clojure 🌿</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo '(println "Hello" (System/getenv "HELLO"))' > index.clj
+
+$ dotenvx run -- clojure -M index.clj
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Kotlin 📐</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo 'fun main() { val hello = System.getenv("HELLO") ?: ""; println("Hello $hello") }' > index.kt
+$ kotlinc index.kt -include-runtime -d index.jar
+
+$ dotenvx run -- java -jar index.jar
+Hello Dotenvx
+```
+
+</details>
+<details><summary>.NET 🔵</summary><br>
+
+```sh
+$ dotnet new console -n HelloWorld -o HelloWorld
+$ cd HelloWorld
+$ echo "HELLO=Dotenvx" | Out-File -FilePath .env -Encoding utf8
+$ echo 'Console.WriteLine($"Hello {Environment.GetEnvironmentVariable("HELLO")}");' > Program.cs
+
+$ dotenvx run -- dotnet run
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Bash 🖥️</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx run --quiet -- sh -c 'echo Hello $HELLO'
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Fish 🐠</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx run --quiet -- sh -c 'echo Hello $HELLO'
+Hello Dotenvx
+```
+
+</details>
+<details><summary>Cron ⏰</summary><br>
+
+```sh
+# run every day at 8am
+0 8 * * * dotenvx run -- /path/to/myscript.sh
+```
+
+</details>
+<details><summary>Frameworks ▲</summary><br>
+
+```sh
+$ dotenvx run -- next dev
+$ dotenvx run -- npm start
+$ dotenvx run -- bin/rails s
+$ dotenvx run -- php artisan serve
+```
+
+see [framework guides](https://dotenvx.com/docs#frameworks)
+
+</details>
+<details><summary>Docker 🐳</summary><br>
+
+```sh
+$ docker run -it --rm -v $(pwd):/app dotenv/dotenvx run -- node index.js
+```
+
+Or in any image:
+
+```Containerfile
+FROM node:latest
+RUN echo "HELLO=Dotenvx" > .env && echo "console.log('Hello ' + process.env.HELLO)" > index.js
+RUN curl -fsS https://dotenvx.sh/install.sh | sh
+CMD ["/usr/local/bin/dotenvx", "run", "--", "echo", "Hello $HELLO"]
+```
+
+see [docker guide](https://dotenvx.com/docs/platforms/docker)
+
+</details>
+<details><summary>CI/CDs 🐙</summary><br>
+
+```yaml
+name: build
+on: [push]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    - uses: actions/setup-node@v3
+      with:
+        node-version: 16
+    - run: curl -fsS https://dotenvx.sh/install.sh | sh
+    - run: dotenvx run -- node build.js
+      env:
+        DOTENV_KEY: ${{ secrets.DOTENV_KEY }}
+```
+
+see [github actions guide](https://dotenvx.com/docs/cis/github-actions)
+
+</details>
+<details><summary>Platforms</summary><br>
+
+```sh
+# heroku
+heroku buildpacks:add https://github.com/dotenvx/heroku-buildpack-dotenvx
+
+# docker
+RUN curl -fsS https://dotenvx.sh | sh
+
+# vercel
+npm install @dotenvx/dotenvx --save
+```
+
+see [platform guides](https://dotenvx.com/docs#platforms)
+
+</details>
+<details><summary>Process Managers</summary><br>
+
+```js
+// pm2
+"scripts": {
+  "start": "dotenvx run -- pm2-runtime start ecosystem.config.js --env production"
+},
+```
+
+see [process manager guides](https://dotenvx.com/docs#process-managers)
+
+</details>
+<details><summary>npx</summary><br>
+
+```sh
+# alternatively use npx
+$ npx @dotenvx/dotenvx run -- node index.js
+$ npx @dotenvx/dotenvx run -- next dev
+$ npx @dotenvx/dotenvx run -- npm start
+```
+
+</details>
+<details><summary>npm</summary><br>
+
+```sh
+$ npm install @dotenvx/dotenvx --save
+```
+
+```json
+{
+  "scripts": {
+    "start": "./node_modules/.bin/dotenvx run -- node index.js"
+  },
+  "dependencies": {
+    "@dotenvx/dotenvx": "^0.5.0"
+  }
+}
+```
+
+```sh
+$ npm run start
+
+> start
+> ./node_modules/.bin/dotenvx run -- node index.js
+
+[dotenvx@1.X.X] injecting env (1) from .env.production
+Hello Dotenvx
+```
+
+</details>
+<details><summary>asdf</summary><br>
+
+```sh
+# use dotenvx with asdf
+$ asdf plugin add dotenvx
+$ asdf install dotenvx latest
+```
+
+thank you [@jgburet](https://github.com/jgburet/asdf-dotenvx) of Paris 🇫🇷
+
+</details>
+<details><summary>Git</summary><br>
+
+```sh
+# use as a git submodule
+$ git dotenvx run -- node index.js
+$ git dotenvx run -- next dev
+$ git dotenvx run -- npm start
+```
+
+</details>
+<details><summary>Variable Expansion</summary><br>
+
+Reference and expand variables already on your machine for use in your .env file.
+
+```ini
+# .env
+USERNAME="username"
+DATABASE_URL="postgres://${USERNAME}@localhost/my_database"
+```
+```js
+// index.js
+console.log('DATABASE_URL', process.env.DATABASE_URL)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@0.14.1] injecting env (2) from .env
+DATABASE_URL postgres://username@localhost/my_database
+```
+
+</details>
+<details><summary>Command Substitution</summary><br>
+
+Add the output of a command to one of your variables in your .env file.
+
+```ini
+# .env
+DATABASE_URL="postgres://$(whoami)@localhost/my_database"
+```
+```js
+// index.js
+console.log('DATABASE_URL', process.env.DATABASE_URL)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@0.14.1] injecting env (1) from .env
+DATABASE_URL postgres://yourusername@localhost/my_database
+```
+
+</details>
+
+
+&nbsp;
+
+## Multiple Environments
+
+> Create a `.env.production` file and use `-f` to load it. It's straightforward, yet flexible.
+```sh
+$ echo "HELLO=production" > .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.production -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.production
+Hello production
+> ^^
+```
+
+More examples
+
+<details><summary>multiple `.env` files</summary><br>
+
+```sh
+$ echo "HELLO=local" > .env.local
+
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx run -f .env.local -f .env -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local,.env
+Hello local
+```
+
+Note subsequent files do NOT override pre-existing variables defined in previous files or env. This follows historic principle. For example, above `local` wins – from the first file.
+
+</details>
+
+<details><summary>`--overload` flag</summary><br>
+
+```sh
+$ echo "HELLO=local" > .env.local
+
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx run -f .env.local -f .env --overload -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local,.env
+Hello Dotenvx
+```
+
+Note that with `--overload` subsequent files DO override pre-existing variables defined in previous files.
+</details>
+<details><summary>`--verbose` flag</summary><br>
+
+```sh
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx run -f .env.production --verbose -- node index.js
+[dotenvx][verbose] injecting env from /path/to/.env.production
+[dotenvx][verbose] HELLO set
+[dotenvx@1.X.X] injecting env (1) from .env.production
+Hello production
+```
+
+</details>
+<details><summary>`--debug` flag</summary><br>
+
+```sh
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx run -f .env.production --debug -- node index.js
+[dotenvx][debug] configuring options
+[dotenvx][debug] {"envFile":[".env.production"]}
+[dotenvx][verbose] injecting env from /path/to/.env.production
+[dotenvx][debug] reading env from /path/to/.env.production
+[dotenvx][debug] parsing env from /path/to/.env.production
+[dotenvx][debug] {"HELLO":"production"}
+[dotenvx][debug] writing env from /path/to/.env.production
+[dotenvx][verbose] HELLO set
+[dotenvx][debug] HELLO set to production
+[dotenvx@1.X.X] injecting env (1) from .env.production
+Hello production
+```
+
+</details>
+<details><summary>`--quiet` flag</summary><br>
+
+Use `--quiet` to suppress all output (except errors).
+
+```sh
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx run -f .env.production --quiet -- node index.js
+Hello production
+```
+
+</details>
+<details><summary>`--log-level` flag</summary><br>
+
+Set `--log-level` to whatever you wish. For example, to suppress warnings (risky), set log level to `error`:
+
+```sh
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx run -f .env.production --log-level=error -- node index.js
+Hello production
+```
+
+Available log levels are `error, warn, info, verbose, debug, silly`
+
+</details>
+<details><summary>`--convention` flag</summary><br>
+
+Load envs using [Next.js' convention](https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#environment-variable-load-order) or [dotenv-flow convention](https://www.npmjs.com/package/dotenv-flow). Set `--convention` to `nextjs` or `flow`:
+
+```sh
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=env" > .env
+
+$ dotenvx run --convention=nextjs -- node index.js
+Hello development local
+
+$ dotenvx run --convention=flow -- node index.js
+Hello development local
+```
+
+(more conventions available upon request)
+
+</details>
+
+&nbsp;
+
+## Encryption
+
+> Add encryption to your `.env` files with a single command. Use `dotenvx encrypt`.
+
+```sh
+$ dotenvx encrypt
+◈ encrypted (.env)
+```
+
+[![encrypted .env](https://github.com/user-attachments/assets/46dfe1a7-a027-4d80-9207-789eccc325dc)](https://dotenvx.com)
+
+> A `DOTENV_PUBLIC_KEY` (encryption key) and a `DOTENV_PRIVATE_KEY` (decryption key) are generated using the same public-key cryptography as [Bitcoin](https://en.bitcoin.it/wiki/Secp256k1).
+
+More examples
+
+<details><summary>`.env`</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`.env.production`</summary><br>
+
+```sh
+$ echo "HELLO=Production" > .env.production
+$ dotenvx encrypt -f .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ DOTENV_PRIVATE_KEY_PRODUCTION="<.env.production private key>" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env.production
+Hello Production
+```
+
+Note the `DOTENV_PRIVATE_KEY_PRODUCTION` ends with `_PRODUCTION`. This instructs `dotenvx run` to load the `.env.production` file.
+
+</details>
+<details><summary>`.env.ci`</summary><br>
+
+```sh
+$ echo "HELLO=Ci" > .env.ci
+$ dotenvx encrypt -f .env.ci
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ DOTENV_PRIVATE_KEY_CI="<.env.ci private key>" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env.ci
+Hello Ci
+```
+
+Note the `DOTENV_PRIVATE_KEY_CI` ends with `_CI`. This instructs `dotenvx run` to load the `.env.ci` file. See the pattern?
+
+</details>
+<details><summary>combine multiple encrypted .env files</summary><br>
+
+```sh
+$ dotenvx set HELLO Dotenvx -f .env
+$ dotenvx set HELLO Production -f .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ DOTENV_PRIVATE_KEY="<.env private key>" DOTENV_PRIVATE_KEY_PRODUCTION="<.env.production private key>" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (3) from .env, .env.production
+Hello Dotenvx
+```
+
+Note the `DOTENV_PRIVATE_KEY` instructs `dotenvx run` to load the `.env` file and the `DOTENV_PRIVATE_KEY_PRODUCTION` instructs it to load the `.env.production` file. See the pattern?
+
+</details>
+<details><summary>combine multiple encrypted .env files for monorepo</summary><br>
+
+```sh
+$ mkdir app1
+$ mkdir app2
+$ dotenvx set HELLO app1 -f app1/.env.ci
+$ dotenvx set HELLO app2 -f app2/.env.ci
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ DOTENV_PRIVATE_KEY_CI="<app1/privat ci key>,<app2/private ci key>" dotenvx run -f app1/.env.ci -f app2/.env.ci -- node index.js
+[dotenvx@1.X.X] injecting env (2) from app1/.env.ci,app2/.env.ci
+Hello app1
+
+$ DOTENV_PRIVATE_KEY_CI="<app1/privat ci key>,<app2/private ci key>" dotenvx run -f app1/.env.ci -f app2/.env.ci --overload -- node index.js
+[dotenvx@1.X.X] injecting env (2) from app1/.env.ci,app2/.env.ci
+Hello app2
+```
+
+Note the `DOTENV_PRIVATE_KEY_CI` (and any `DOTENV_PRIVATE_KEY*`) can take multiple private keys by simply comma separating them.
+
+</details>
+<details><summary>`--stdout`</summary><br>
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt --stdout
+$ dotenvx encrypt --stdout > .env.encrypted
+```
+
+</details>
+
+<details><summary>other curves</summary><br>
+
+> `secp256k1` is a well-known and battle tested curve, in use with Bitcoin and other cryptocurrencies, but we are open to adding support for more curves.
+> 
+> If your organization's compliance department requires [NIST approved curves](https://csrc.nist.gov/projects/elliptic-curve-cryptography) or other curves like `curve25519`, please reach out at [security@dotenvx.com](mailto:security@dotenvx.com).
+
+</details>
+
+&nbsp;
+
+## Advanced
+
+> Become a `dotenvx` power user.
+>
+
+### CLI 📟
+
+Advanced CLI commands.
+
+<details><summary>`run` - Variable Expansion</summary><br>
+
+Reference and expand variables already on your machine for use in your .env file.
+
+```ini
+# .env
+USERNAME="username"
+DATABASE_URL="postgres://${USERNAME}@localhost/my_database"
+```
+```js
+// index.js
+console.log('DATABASE_URL', process.env.DATABASE_URL)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env
+DATABASE_URL postgres://username@localhost/my_database
+```
+
+</details>
+<details><summary>`run` - Default Values</summary><br>
+
+Use default values when environment variables are unset or empty.
+
+```ini
+# .env
+# Default value syntax: use value if set, otherwise use default
+DATABASE_HOST=${DB_HOST:-localhost}
+DATABASE_PORT=${DB_PORT:-5432}
+
+# Alternative syntax (no colon): use value if set, otherwise use default
+API_URL=${API_BASE_URL-https://api.example.com}
+```
+```js
+// index.js
+console.log('DATABASE_HOST', process.env.DATABASE_HOST)
+console.log('DATABASE_PORT', process.env.DATABASE_PORT)
+console.log('API_URL', process.env.API_URL)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@1.X.X] injecting env (3) from .env
+DATABASE_HOST localhost
+DATABASE_PORT 5432
+API_URL https://api.example.com
+```
+
+</details>
+<details><summary>`run` - Alternate Values</summary><br>
+
+Use alternate values when environment variables are set and non-empty.
+
+```ini
+# .env
+NODE_ENV=production
+
+# Alternate value syntax: use alternate if set and non-empty, otherwise empty
+DEBUG_MODE=${NODE_ENV:+false}
+LOG_LEVEL=${NODE_ENV:+error}
+
+# Alternative syntax (no colon): use alternate if set, otherwise empty  
+CACHE_ENABLED=${NODE_ENV+true}
+```
+```js
+// index.js
+console.log('NODE_ENV', process.env.NODE_ENV)
+console.log('DEBUG_MODE', process.env.DEBUG_MODE)
+console.log('LOG_LEVEL', process.env.LOG_LEVEL)
+console.log('CACHE_ENABLED', process.env.CACHE_ENABLED)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@1.X.X] injecting env (4) from .env
+NODE_ENV production
+DEBUG_MODE false
+LOG_LEVEL error
+CACHE_ENABLED true
+```
+
+</details>
+<details><summary>`run` - Interpolation Syntax Summary (Variable Expansion, Default/Alternate Values)</summary><br>
+
+Complete reference for variable interpolation patterns supported by dotenvx:
+
+```ini
+# .env
+DEFINED_VAR=hello
+EMPTY_VAR=
+# UNDEFINED_VAR is not set
+
+# Default value syntax - use variable if set/non-empty, otherwise use default
+TEST1=${DEFINED_VAR:-fallback}     # Result: "hello"
+TEST2=${EMPTY_VAR:-fallback}       # Result: "fallback"  
+TEST3=${UNDEFINED_VAR:-fallback}   # Result: "fallback"
+
+# Default value syntax (no colon) - use variable if set, otherwise use default
+TEST4=${DEFINED_VAR-fallback}      # Result: "hello"
+TEST5=${EMPTY_VAR-fallback}        # Result: "" (empty, but set)
+TEST6=${UNDEFINED_VAR-fallback}    # Result: "fallback"
+
+# Alternate value syntax - use alternate if variable is set/non-empty, otherwise empty
+TEST7=${DEFINED_VAR:+alternate}    # Result: "alternate"
+TEST8=${EMPTY_VAR:+alternate}      # Result: "" (empty)
+TEST9=${UNDEFINED_VAR:+alternate}  # Result: "" (empty)
+
+# Alternate value syntax (no colon) - use alternate if variable is set, otherwise empty  
+TEST10=${DEFINED_VAR+alternate}    # Result: "alternate"
+TEST11=${EMPTY_VAR+alternate}      # Result: "alternate" (empty but set)
+TEST12=${UNDEFINED_VAR+alternate}  # Result: "" (empty)
+```
+
+**Key differences:**
+- `:-` vs `-`: The colon makes empty values trigger the fallback
+- `:+` vs `+`: The colon makes empty values not trigger the alternate  
+- Default syntax (`-`): Use variable value or fallback
+- Alternate syntax (`+`): Use alternate value or empty string
+
+</details>
+<details><summary>`run` - Command Substitution</summary><br>
+
+Add the output of a command to one of your variables in your .env file.
+
+```ini
+# .env
+DATABASE_URL="postgres://$(whoami)@localhost/my_database"
+```
+```js
+// index.js
+console.log('DATABASE_URL', process.env.DATABASE_URL)
+```
+```sh
+$ dotenvx run --debug -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env
+DATABASE_URL postgres://yourusername@localhost/my_database
+```
+
+</details>
+<details><summary>`run` - Shell Expansion</summary><br>
+
+Prevent your shell from expanding inline `$VARIABLES` before dotenvx has a chance to inject it. Use a subshell.
+
+```sh
+$ dotenvx run --env="HELLO=Dotenvx" -- sh -c 'echo Hello $HELLO'
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`run` - Multiline</summary><br>
+
+Dotenvx supports multiline values. This is particularly useful in conjunction with Docker - which [does not support multiline values](https://stackoverflow.com/questions/50299617/set-multiline-environment-variable-with-dockerfile/79578348#79578348).
+
+```ini
+# .env
+MULTILINE_PEM="-----BEGIN PUBLIC KEY-----
+MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnNl1tL3QjKp3DZWM0T3u
+LgGJQwu9WqyzHKZ6WIA5T+7zPjO1L8l3S8k8YzBrfH4mqWOD1GBI8Yjq2L1ac3Y/
+bTdfHN8CmQr2iDJC0C6zY8YV93oZB3x0zC/LPbRYpF8f6OqX1lZj5vo2zJZy4fI/
+kKcI5jHYc8VJq+KCuRZrvn+3V+KuL9tF9v8ZgjF2PZbU+LsCy5Yqg1M8f5Jp5f6V
+u4QuUoobAgMBAAE=
+-----END PUBLIC KEY-----"
+```
+
+```js
+// index.js
+console.log('MULTILINE_PEM', process.env.MULTILINE_PEM)
+```
+
+```sh
+$ dotenvx run -- node index.js
+MULTILINE_PEM -----BEGIN PUBLIC KEY-----
+MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnNl1tL3QjKp3DZWM0T3u
+LgGJQwu9WqyzHKZ6WIA5T+7zPjO1L8l3S8k8YzBrfH4mqWOD1GBI8Yjq2L1ac3Y/
+bTdfHN8CmQr2iDJC0C6zY8YV93oZB3x0zC/LPbRYpF8f6OqX1lZj5vo2zJZy4fI/
+kKcI5jHYc8VJq+KCuRZrvn+3V+KuL9tF9v8ZgjF2PZbU+LsCy5Yqg1M8f5Jp5f6V
+u4QuUoobAgMBAAE=
+-----END PUBLIC KEY-----
+```
+
+</details>
+<details><summary>`run` - Contextual Help</summary><br>
+
+Unlike other dotenv libraries, dotenvx attempts to unblock you with contextual help.
+
+For example, when missing a custom .env file:
+
+```sh
+$ dotenvx run -f .env.missing -- echo $HELLO
+[MISSING_ENV_FILE] missing file (/Users/scottmotte/Code/dotenvx/playground/apr-16/.env.missing). fix: [echo "HELLO=Dotenvx" > .env.missing]
+```
+
+or when missing a KEY:
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx get GOODBYE
+[MISSING_KEY] missing key (GOODBYE)
+```
+
+</details>
+<details><summary>`run` - multiple `-f` flags</summary><br>
+
+Compose multiple `.env` files for environment variables loading, as you need.
+
+```sh
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=Dotenvx" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.local -f .env -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local, .env
+Hello local
+```
+
+Note subsequent files do NOT override pre-existing variables defined in previous files or env. This follows historic principle. For example, above `local` wins – from the first file.
+
+</details>
+<details><summary>`run --env HELLO=String`</summary><br>
+
+Set environment variables as a simple `KEY=value` string pair.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run --env HELLO=String -f .env -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env, and --env flag
+Hello String
+```
+
+</details>
+<details><summary>`run --overload`</summary><br>
+
+Override existing env variables. These can be variables already on your machine or variables loaded as files consecutively. The last variable seen will 'win'.
+
+```sh
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=Dotenvx" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.local -f .env --overload -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local, .env
+Hello Dotenvx
+```
+
+Note that with `--overload` subsequent files DO override pre-existing variables defined in previous files.
+
+</details>
+<details><summary>`run` - Environment Variable Precedence (Container/Cloud Deployments)</summary><br>
+
+When deploying applications in containers or cloud environments, you often need to override specific environment variables at runtime without modifying committed `.env` files. By default, dotenvx follows the historic dotenv principle: **environment variables already present take precedence over `.env` files**.
+
+```sh
+# .env.prod contains: MODEL_REGISTRY=registry.company.com/models/v1
+$ echo "MODEL_REGISTRY=registry.company.com/models/v1" > .env.prod
+$ echo "console.log('MODEL_REGISTRY:', process.env.MODEL_REGISTRY)" > app.js
+
+# Without environment variable set - uses .env.prod value
+$ dotenvx run -f .env.prod -- node app.js
+MODEL_REGISTRY: registry.company.com/models/v1
+
+# With environment variable set (e.g., via Azure Container Service) - environment variable takes precedence
+$ MODEL_REGISTRY=registry.azure.com/models/v2 dotenvx run -f .env.prod -- node app.js
+MODEL_REGISTRY: registry.azure.com/models/v2
+
+# To force .env.prod to override environment variables, use --overload
+$ MODEL_REGISTRY=registry.azure.com/models/v2 dotenvx run -f .env.prod --overload -- node app.js
+MODEL_REGISTRY: registry.company.com/models/v1
+```
+
+**For container deployments:** Set environment variables through your cloud provider's UI/configuration (Azure Container Service, AWS ECS, etc.) to override specific values from committed `.env` files without rebuilding your application.
+
+</details>
+<details><summary>`DOTENV_PRIVATE_KEY=key run`</summary><br>
+
+Decrypt your encrypted `.env` by setting `DOTENV_PRIVATE_KEY` before `dotenvx run`.
+
+```sh
+$ touch .env
+$ dotenvx set HELLO encrypted
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+# check your .env.keys files for your privateKey
+$ DOTENV_PRIVATE_KEY="122...0b8" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env
+Hello encrypted
+```
+
+</details>
+<details><summary>`DOTENV_PRIVATE_KEY_PRODUCTION=key run`</summary><br>
+
+Decrypt your encrypted `.env.production` by setting `DOTENV_PRIVATE_KEY_PRODUCTION` before `dotenvx run`. Alternatively, this can be already set on your server or cloud provider.
+
+```sh
+$ touch .env.production
+$ dotenvx set HELLO "production encrypted" -f .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+# check .env.keys for your privateKey
+$ DOTENV_PRIVATE_KEY_PRODUCTION="122...0b8" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env.production
+Hello production encrypted
+```
+
+Note the `DOTENV_PRIVATE_KEY_PRODUCTION` ends with `_PRODUCTION`. This instructs dotenvx run to load the `.env.production` file.
+
+</details>
+<details><summary>`DOTENV_PRIVATE_KEY_CI=key dotenvx run`</summary><br>
+
+Decrypt your encrypted `.env.ci` by setting `DOTENV_PRIVATE_KEY_CI` before `dotenvx run`. Alternatively, this can be already set on your server or cloud provider.
+
+```sh
+$ touch .env.ci
+$ dotenvx set HELLO "ci encrypted" -f .env.ci
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+# check .env.keys for your privateKey
+$ DOTENV_PRIVATE_KEY_CI="122...0b8" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (2) from .env.ci
+Hello ci encrypted
+```
+
+Note the `DOTENV_PRIVATE_KEY_CI` ends with `_CI`. This instructs dotenvx run to load the `.env.ci` file. See the pattern?
+
+</details>
+<details><summary>`DOTENV_PRIVATE_KEY=key DOTENV_PRIVATE_KEY_PRODUCTION=key run` - Combine Multiple</summary><br>
+
+Decrypt your encrypted `.env` and `.env.production` files by setting `DOTENV_PRIVATE_KEY` and `DOTENV_PRIVATE_KEY_PRODUCTION` before `dotenvx run`. 
+
+```sh
+$ touch .env
+$ touch .env.production
+$ dotenvx set HELLO encrypted
+$ dotenvx set HELLO "production encrypted" -f .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+# check .env.keys for your privateKeys
+$ DOTENV_PRIVATE_KEY="122...0b8" DOTENV_PRIVATE_KEY_PRODUCTION="122...0b8" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (3) from .env, .env.production
+Hello encrypted
+
+$ DOTENV_PRIVATE_KEY_PRODUCTION="122...0b8" DOTENV_PRIVATE_KEY="122...0b8" dotenvx run -- node index.js
+[dotenvx@1.X.X] injecting env (3) from .env.production, .env
+Hello production encrypted
+```
+
+Compose any encrypted files you want this way. As long as a `DOTENV_PRIVATE_KEY_${environment}` is set, the values from `.env.${environment}` will be decrypted at runtime.
+
+</details>
+<details><summary>`run --verbose`</summary><br>
+
+Set log level to `verbose`. ([log levels](https://docs.npmjs.com/cli/v8/using-npm/logging#setting-log-levels))
+
+```sh
+$ echo "HELLO=production" > .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.production --verbose -- node index.js
+loading env from .env.production (/path/to/.env.production)
+HELLO set
+[dotenvx@1.X.X] injecting env (1) from .env.production
+Hello production
+```
+
+</details>
+<details><summary>`run --debug`</summary><br>
+
+Set log level to `debug`. ([log levels](https://docs.npmjs.com/cli/v8/using-npm/logging#setting-log-levels))
+
+```sh
+$ echo "HELLO=production" > .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.production --debug -- node index.js
+process command [node index.js]
+options: {"env":[],"envFile":[".env.production"]}
+loading env from .env.production (/path/to/.env.production)
+{"HELLO":"production"}
+HELLO set
+HELLO set to production
+[dotenvx@1.X.X] injecting env (1) from .env.production
+executing process command [node index.js]
+expanding process command to [/opt/homebrew/bin/node index.js]
+Hello production
+```
+
+</details>
+<details><summary>`run --quiet`</summary><br>
+
+Use `--quiet` to suppress all output (except errors). ([log levels](https://docs.npmjs.com/cli/v8/using-npm/logging#setting-log-levels))
+
+```sh
+$ echo "HELLO=production" > .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.production --quiet -- node index.js
+Hello production
+```
+
+</details>
+<details><summary>`run --log-level`</summary><br>
+
+Set `--log-level` to whatever you wish. For example, to suppress warnings (risky), set log level to `error`:
+
+```sh
+$ echo "HELLO=production" > .env.production
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.production --log-level=error -- node index.js
+Hello production
+```
+
+Available log levels are `error, warn, info, verbose, debug, silly` ([source](https://docs.npmjs.com/cli/v8/using-npm/logging#setting-log-levels))
+
+</details>
+<details><summary>`run --strict`</summary><br>
+
+Exit with code `1` if any errors are encountered - like a missing .env file or decryption failure.
+
+```sh
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.missing --strict -- node index.js
+[MISSING_ENV_FILE] missing file (/path/to/.env.missing). fix: [echo "HELLO=Dotenvx" > .env.missing]
+```
+
+This can be useful in `ci` scripts where you want to fail the ci if your `.env` file could not be decrypted at runtime.
+
+</details>
+<details><summary>`run --ignore`</summary><br>
+
+Ignore errors like `MISSING_ENV_FILE`.
+
+```sh
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run -f .env.missing --ignore=MISSING_ENV_FILE -- node index.js
+...
+```
+
+</details>
+<details><summary>`run --convention=nextjs`</summary><br>
+
+Load envs using [Next.js' convention](https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#environment-variable-load-order). Set `--convention` to `nextjs`:
+
+```sh
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=env" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx run --convention=nextjs -- node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.development.local, .env.local, .env.development, .env
+Hello development local
+```
+
+(more conventions available upon request)
+
+</details>
+<details><summary>`run --convention=flow`</summary><br>
+
+Load envs using [dotenv-flow's convention](https://www.npmjs.com/package/dotenv-flow). Set `--convention` to `flow`:
+
+```sh
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=env" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ NODE_ENV=development dotenvx run --convention=flow -- node index.js 
+[dotenvx@1.X.X] injecting env (1) from .env.development.local, .env.development, .env.local, .env
+Hello development local
+```
+
+Further, we recommend using `DOTENV_ENV` over `NODE_ENV`– as `dotenvx` works everywhere, not just node.
+
+```sh
+$ DOTENV_ENV=development dotenvx run --convention=flow -- node index.js 
+[dotenvx@1.X.X] injecting env (1) from .env.development.local, .env.development, .env.local, .env
+Hello development local
+```
+
+</details>
+<details><summary>`run -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ touch apps/app1/.env
+$ dotenvx set HELLO Dotenvx -fk .env.keys -f apps/app1/.env
+
+$ dotenvx run -fk .env.keys -f apps/app1/.env -- yourcommand
+```
+
+</details>
+<details><summary>`run --token`</summary><br>
+
+Set Armor ⛨ token for retrieving armored private keys.
+
+```sh
+$ dotenvx run --token "$DOTENVX_ARMOR_TOKEN" -- yourcommand
+```
+
+</details>
+<details><summary>`run --no-armor`</summary><br>
+
+Turn off [Dotenvx Armor ⛨](https://dotenvx.com/armor) features.
+
+```sh
+$ dotenvx run --no-armor -- yourcommand
+```
+
+`--no-vlt` and `--no-ops` are deprecated aliases.
+
+</details>
+<details><summary>`get KEY`</summary><br>
+
+Return a single environment variable's value.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx get HELLO
+World
+```
+
+</details>
+<details><summary>`get KEY -f`</summary><br>
+
+Return a single environment variable's value from a specific `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx get HELLO -f .env.production
+production
+```
+
+</details>
+<details><summary>`get KEY -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ touch apps/app1/.env
+$ dotenvx set HELLO Dotenvx -fk .env.keys -f apps/app1/.env
+
+$ dotenvx get HELLO -fk .env.keys -f apps/app1/.env
+world
+```
+
+</details>
+<details><summary>`get KEY --env`</summary><br>
+
+Return a single environment variable's value from a `--env` string.
+
+```sh
+$ dotenvx get HELLO --env HELLO=String -f .env.production
+String
+```
+
+</details>
+
+<details><summary>`get KEY --overload`</summary><br>
+
+Return a single environment variable's value where each found value is overloaded.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "HELLO=production" > .env.production
+
+$ dotenvx get HELLO -f .env.production --env HELLO=String -f .env --overload
+World
+```
+
+</details>
+<details><summary>`get KEY --strict`</summary><br>
+
+Exit with code `1` if any errors are encountered - like a missing key, missing .env file, or decryption failure.
+
+```sh
+$ dotenvx get DOES_NOT_EXIST --strict
+[MISSING_KEY] missing key (DOES_NOT_EXIST)
+```
+
+</details>
+<details><summary>`get KEY --convention=nextjs`</summary><br>
+
+Return a single environment variable's value using [Next.js' convention](https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#environment-variable-load-order). Set `--convention` to `nextjs`:
+
+```sh
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=env" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ dotenvx get HELLO --convention=nextjs
+development local
+```
+
+</details>
+<details><summary>`get KEY --convention=flow`</summary><br>
+
+Return a single environment variable's value using [dotenv-flow's convention](https://www.npmjs.com/package/dotenv-flow). Set `--convention` to `flow`:
+
+```sh
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=env" > .env
+$ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+$ NODE_ENV=development dotenvx get HELLO --convention=flow
+development local
+```
+
+Further, we recommend using `DOTENV_ENV` over `NODE_ENV`– as `dotenvx` works everywhere, not just node.
+
+```sh
+$ DOTENV_ENV=development dotenvx get HELLO --convention=flow
+development local
+```
+
+</details>
+<details><summary>`get` (json)</summary><br>
+
+Return a json response of all key/value pairs in a `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx get
+{"HELLO":"Dotenvx"}
+```
+
+</details>
+<details><summary>`get --format shell`</summary><br>
+
+Return a shell formatted response of all key/value pairs in a `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "KEY=value" >> .env
+
+$ dotenvx get --format shell
+HELLO=Dotenvx KEY=value
+```
+
+This can be useful when combined with `env` on the command line.
+
+```
+$ echo "console.log('Hello ' + process.env.KEY + ' ' + process.env.HELLO)" > index.js
+$ env $(dotenvx get --format=shell) node index.js
+Hello value World
+```
+
+or with `export`.
+
+```
+$ echo "console.log('Hello ' + process.env.KEY + ' ' + process.env.HELLO)" > index.js
+$ export $(dotenvx get --format=shell)
+$ node index.js
+Hello value World
+```
+
+</details>
+<details><summary>`get --format eval`</summary><br>
+
+Return an `eval`-ready shell formatted response of all key/value pairs in a `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "KEY=value" >> .env
+
+$ dotenvx get --format eval
+HELLO="Dotenvx"
+KEY="value"
+```
+
+Note that this exports newlines and quoted strings.
+
+This can be useful for more complex .env values (spaces, escaped characters, quotes, etc) combined with `eval` on the command line.
+
+```sh
+$ echo "console.log('Hello ' + process.env.KEY + ' ' + process.env.HELLO)" > index.js
+$ eval $(dotenvx get --format=eval) node index.js
+Hello value World
+```
+
+Be careful with `eval` as it allows for arbitrary execution of commands. Prefer `dotenvx run --` but in some cases `eval` is a sharp knife that is useful to have.
+
+</details>
+
+<details><summary>`get --all`</summary><br>
+
+Return preset machine envs as well.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx get --all
+{"PWD":"/some/file/path","USER":"username","LIBRARY_PATH":"/usr/local/lib", ..., "HELLO":"Dotenvx"}
+```
+
+</details>
+<details><summary>`get --all --pretty-print`</summary><br>
+
+Make the output more readable - pretty print it.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx get --all --pretty-print
+{
+  "PWD": "/some/filepath",
+  "USER": "username",
+  "LIBRARY_PATH": "/usr/local/lib",
+  ...,
+  "HELLO": "Dotenvx"
+}
+```
+
+</details>
+<details><summary>`set KEY value`</summary><br>
+
+Set an encrypted key/value (on by default).
+
+```sh
+$ touch .env
+
+$ dotenvx set HELLO Dotenvx
+set HELLO with encryption (.env)
+```
+
+</details>
+<details><summary>`set KEY value -f`</summary><br>
+
+Set an (encrypted) key/value for another `.env` file.
+
+```sh
+$ touch .env.production
+
+$ dotenvx set HELLO production -f .env.production
+set HELLO with encryption (.env.production)
+```
+
+</details>
+<details><summary>`set KEY value -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ touch apps/app1/.env
+
+$ dotenvx set HELLO Dotenvx -fk .env.keys -f apps/app1/.env
+set HELLO with encryption (.env)
+```
+
+Put it to use.
+
+```sh
+$ dotenvx get -fk .env.keys -f apps/app1/.env
+```
+
+Use it with a relative path.
+
+```sh
+$ cd apps/app1
+$ dotenvx get -fk ../../.env.keys -f .env
+```
+
+</details>
+<details><summary>`set KEY "value with spaces"`</summary><br>
+
+Set a value containing spaces.
+
+```sh
+$ touch .env.ci
+
+$ dotenvx set HELLO "my ci" -f .env.ci
+set HELLO with encryption (.env.ci)
+```
+
+</details>
+<details><summary>`set KEY -- "- + * ÷"`</summary><br>
+
+If your value starts with a dash (`-`), then place two dashes instructing the cli that there are no more flag arguments.
+
+```sh
+$ touch .env.ci
+
+$ dotenvx set HELLO -f .env.ci -- "- + * ÷"
+set HELLO with encryption (.env.ci)
+```
+
+</details>
+<details><summary>`set KEY value --plain`</summary><br>
+
+Set a plaintext key/value.
+
+```sh
+$ touch .env
+
+$ dotenvx set HELLO Dotenvx --plain
+set HELLO (.env)
+```
+
+</details>
+<details><summary>`encrypt`</summary><br>
+
+Encrypt the contents of a `.env` file to an encrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx encrypt
+◈ encrypted (.env) + local key (.env.keys)
+⮕  next run [dotenvx ext gitignore --pattern .env.keys] to gitignore .env.keys
+⮕  next run [DOTENV_PRIVATE_KEY='122...0b8' dotenvx run -- yourcommand] to test decryption locally
+```
+
+</details>
+<details><summary>`encrypt -f`</summary><br>
+
+Encrypt the contents of a specified `.env` file to an encrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "HELLO=Production" > .env.production
+
+$ dotenvx encrypt -f .env.production
+◈ encrypted (.env.production) + local key (.env.keys)
+⮕  next run [dotenvx ext gitignore --pattern .env.keys] to gitignore .env.keys
+⮕  next run [DOTENV_PRIVATE_KEY='bff...bc4' dotenvx run -- yourcommand] to test decryption locally
+```
+
+</details>
+<details><summary>`encrypt --no-armor`</summary><br>
+
+Turn off [Dotenvx Armor ⛨](https://dotenvx.com/armor) features for encrypt.
+
+```sh
+$ dotenvx encrypt --no-armor
+◈ encrypted (.env)
+```
+
+`--no-vlt` and `--no-ops` are deprecated aliases.
+
+</details>
+<details><summary>`encrypt -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ echo "HELLO=Dotenvx" > apps/app1/.env
+
+$ dotenvx encrypt -fk .env.keys -f apps/app1/.env
+◈ encrypted (apps/app1/.env)
+```
+
+Put it to use.
+
+```sh
+$ dotenvx run -fk .env.keys -f apps/app1/.env
+```
+
+Use with a relative path.
+
+```sh
+$ cd apps/app1
+$ dotenvx run -fk ../../.env.keys -f .env
+```
+
+</details>
+<details><summary>`encrypt -k`</summary><br>
+
+Specify the key(s) to encrypt by passing `--key`.
+
+```sh
+$ echo "HELLO=Dotenvx\nHELLO2=Universe" > .env
+
+$ dotenvx encrypt -k HELLO2
+◈ encrypted (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+
+$ dotenvx encrypt -k "HE*"
+◈ encrypted (.env)
+```
+
+</details>
+<details><summary>`encrypt -ek`</summary><br>
+
+Specify the key(s) to NOT encrypt by passing `--exclude-key`.
+
+```sh
+$ echo "HELLO=Dotenvx\nHELLO2=Universe" > .env
+
+$ dotenvx encrypt -ek HELLO
+◈ encrypted (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+
+$ dotenvx encrypt -ek "HO*"
+◈ encrypted (.env)
+```
+
+</details>
+<details><summary>`encrypt --stdout`</summary><br>
+
+Encrypt the contents of a `.env` file and send to stdout.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt --stdout
+#/-------------------[DOTENV_PUBLIC_KEY]--------------------/
+#/            public-key encryption for .env files          /
+#/       [how it works](https://dotenvx.com/encryption)     /
+#/----------------------------------------------------------/
+DOTENV_PUBLIC_KEY="034af93e93708b994c10f236c96ef88e47291066946cce2e8d98c9e02c741ced45"
+# .env
+HELLO="encrypted:BDqDBibm4wsYqMpCjTQ6BsDHmMadg9K3dAt+Z9HPMfLEIRVz50hmLXPXRuDBXaJi/LwWYEVUNiq0HISrslzQPaoyS8Lotg3gFWJTsNCdOWnqpjF2xNUX2RQiP05kAbEXM6MWVjDr"
+```
+
+or send to a file:
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt --stdout > somefile.txt
+```
+
+</details>
+<details><summary>`decrypt`</summary><br>
+
+Decrypt the contents of an encrypted `.env` file to an unencrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx decrypt
+◇ decrypted (.env)
+```
+
+</details>
+<details><summary>`decrypt -f`</summary><br>
+
+Decrypt the contents of a specified encrypted `.env` file to an unencrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "HELLO=Production" > .env.production
+
+$ dotenvx encrypt -f .env.production
+◈ encrypted (.env.production)
+$ dotenvx decrypt -f .env.production
+◇ decrypted (.env.production)
+```
+
+</details>
+<details><summary>`decrypt -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ echo "HELLO=Dotenvx" > apps/app1/.env
+
+$ dotenvx encrypt -fk .env.keys -f apps/app1/.env
+◈ encrypted (apps/app1/.env)
+$ dotenvx decrypt -fk .env.keys -f apps/app1/.env
+◇ decrypted (apps/app1/.env)
+```
+
+</details>
+<details><summary>`decrypt -k`</summary><br>
+
+Decrypt the contents of a specified key inside an encrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx decrypt -k HELLO
+◇ decrypted (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx decrypt -k "HE*"
+◇ decrypted (.env)
+```
+
+</details>
+<details><summary>`decrypt -ek`</summary><br>
+
+Decrypt the contents inside an encrypted `.env` file except for an excluded key.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx decrypt -ek HOLA
+◇ decrypted (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx decrypt -ek "HO*"
+◇ decrypted (.env)
+```
+
+</details>
+<details><summary>`decrypt --stdout`</summary><br>
+
+Decrypt the contents of an encrypted `.env` file and send to stdout.
+
+```sh
+$ dotenvx decrypt --stdout
+#/-------------------[DOTENV_PUBLIC_KEY]--------------------/
+#/            public-key encryption for .env files          /
+#/       [how it works](https://dotenvx.com/encryption)     /
+#/----------------------------------------------------------/
+DOTENV_PUBLIC_KEY="034af93e93708b994c10f236c96ef88e47291066946cce2e8d98c9e02c741ced45"
+# .env
+HELLO="Dotenvx"
+```
+
+or send to a file:
+
+```sh
+$ dotenvx decrypt --stdout > somefile.txt
+```
+
+</details>
+<details><summary>`keypair`</summary><br>
+
+Print public/private keys for `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt
+
+$ dotenvx keypair
+{"DOTENV_PUBLIC_KEY":"<publicKey>","DOTENV_PRIVATE_KEY":"<privateKey>"}
+```
+
+</details>
+<details><summary>`keypair -f`</summary><br>
+
+Print public/private keys for `.env.production` file.
+
+```sh
+$ echo "HELLO=Production" > .env.production
+$ dotenvx encrypt -f .env.production
+
+$ dotenvx keypair -f .env.production
+{"DOTENV_PUBLIC_KEY_PRODUCTION":"<publicKey>","DOTENV_PRIVATE_KEY_PRODUCTION":"<privateKey>"}
+```
+
+</details>
+<details><summary>`keypair -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful for printing public/private keys for monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ echo "HELLO=Dotenvx" > apps/app1/.env
+$ dotenvx encrypt -fk .env.keys -f apps/app1/.env
+
+$ dotenvx keypair -fk .env.keys -f apps/app1/.env
+{"DOTENV_PUBLIC_KEY":"<publicKey>","DOTENV_PRIVATE_KEY":"<privateKey>"}
+```
+
+</details>
+<details><summary>`keypair DOTENV_PRIVATE_KEY`</summary><br>
+
+Print specific keypair for `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt
+
+$ dotenvx keypair DOTENV_PRIVATE_KEY
+<privateKey>
+```
+
+</details>
+<details><summary>`keypair --format shell`</summary><br>
+
+Print a shell formatted response of public/private keys.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenx encrypt
+
+$ dotenvx keypair --format shell
+DOTENV_PUBLIC_KEY=<publicKey> DOTENV_PRIVATE_KEY=<privateKey>
+```
+
+</details>
+<details><summary>`ls`</summary><br>
+
+Print all `.env` files in a tree structure.
+
+```sh
+$ touch .env
+$ touch .env.production
+$ mkdir -p apps/backend
+$ touch apps/backend/.env
+
+$ dotenvx ls
+├─ .env.production
+├─ .env
+└─ apps
+   └─ backend
+      └─ .env
+```
+
+</details>
+<details><summary>`ls directory`</summary><br>
+
+Print all `.env` files inside a specified path to a directory.
+
+```sh
+$ touch .env
+$ touch .env.production
+$ mkdir -p apps/backend
+$ touch apps/backend/.env
+
+$ dotenvx ls apps/backend
+└─ .env
+```
+
+</details>
+<details><summary>`ls -f`</summary><br>
+
+Glob `.env` filenames matching a wildcard.
+
+```sh
+$ touch .env
+$ touch .env.production
+$ mkdir -p apps/backend
+$ touch apps/backend/.env
+$ touch apps/backend/.env.prod
+
+$ dotenvx ls -f **/.env.prod*
+├─ .env.production
+└─ apps
+   └─ backend
+      └─ .env.prod
+```
+
+</details>
+<details><summary>`ls -ef`</summary><br>
+
+Glob `.env` filenames excluding a wildcard.
+
+```sh
+$ touch .env
+$ touch .env.production
+$ mkdir -p apps/backend
+$ touch apps/backend/.env
+$ touch apps/backend/.env.prod
+
+$ dotenvx ls -ef '**/.env.prod*'
+├─ .env
+└─ apps
+   └─ backend
+      └─ .env
+```
+
+</details>
+<details><summary>`rotate`</summary><br>
+
+Rotate public/private keys for `.env` file and re-encrypt all encrypted values.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx rotate
+⟳ rotated (.env)
+```
+
+</details>
+<details><summary>`rotate -f`</summary><br>
+
+Rotate public/private keys for a specified encrypted `.env` file and re-encrypt all encrypted values.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "HELLO=Production" > .env.production
+
+$ dotenvx encrypt -f .env.production
+◈ encrypted (.env.production)
+$ dotenvx rotate -f .env.production
+⟳ rotated (.env.production)
+```
+
+</details>
+<details><summary>`rotate -fk`</summary><br>
+
+Specify path to `.env.keys`. This is useful with monorepos.
+
+```sh
+$ mkdir -p apps/app1
+$ echo "HELLO=Dotenvx" > apps/app1/.env
+
+$ dotenvx encrypt -fk .env.keys -f apps/app1/.env
+◈ encrypted (apps/app1/.env)
+$ dotenvx rotate -fk .env.keys -f apps/app1/.env
+⟳ rotated (apps/app1/.env)
+```
+
+</details>
+<details><summary>`rotate -k`</summary><br>
+
+Rotate the contents of a specified key inside an encrypted `.env` file.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx rotate -k HELLO
+⟳ rotated (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx rotate -k "HE*"
+⟳ rotated (.env)
+```
+
+</details>
+<details><summary>`rotate -ek`</summary><br>
+
+Rotate the encrypted contents inside an encrypted `.env` file except for an excluded key.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx rotate -ek HOLA
+⟳ rotated (.env)
+```
+
+Even specify a glob pattern.
+
+```sh
+$ echo "HELLO=Dotenvx\nHOLA=Mundo" > .env
+$ dotenvx encrypt
+◈ encrypted (.env)
+$ dotenvx rotate -ek "HO*"
+⟳ rotated (.env)
+```
+
+</details>
+<details><summary>`rotate --stdout`</summary><br>
+
+Rotate the contents of an encrypted `.env` file and send to stdout.
+
+```sh
+$ dotenvx rotate --stdout
+#/-------------------[DOTENV_PUBLIC_KEY]--------------------/
+#/            public-key encryption for .env files          /
+#/       [how it works](https://dotenvx.com/encryption)     /
+#/----------------------------------------------------------/
+DOTENV_PUBLIC_KEY="034af93e93708b994c10f236c96ef88e47291066946cce2e8d98c9e02c741ced45"
+# .env
+HELLO="encrypted:12345"
+```
+
+or send to a file:
+
+```sh
+$ dotenvx rotate --stdout > somefile.txt
+```
+
+</details>
+<details><summary>`help`</summary><br>
+
+Output help for `dotenvx`.
+
+```sh
+$ dotenvx help
+Usage: dotenvx run -- yourcommand
+
+a secure dotenv–from the creator of `dotenv`
+
+Options:
+  -l, --log-level <level>      set log level (default: "info")
+  -q, --quiet                  sets log level to error
+  -v, --verbose                sets log level to verbose
+  -d, --debug                  sets log level to debug
+  -V, --version                output the version number
+  -h, --help                   display help for command
+
+Commands:
+  run                inject env at runtime [dotenvx run -- yourcommand]
+  get [KEY]          return a single environment variable
+  set <KEY> <value>  set a single environment variable
+  encrypt            encrypt .env file(s)
+  decrypt            decrypt .env file(s)
+  keypair [KEY]      print public/private keys for .env file(s)
+  ls [directory]     print all .env files in a tree structure
+ 
+Advanced: 
+  pro                          🏆 pro
+  ext                          🔌 extensions
+```
+
+You can get more detailed help per command with `dotenvx help COMMAND`.
+
+```sh
+$ dotenvx help run
+Usage: @dotenvx/dotenvx run [options]
+
+inject env at runtime [dotenvx run -- yourcommand]
+
+Options:
+  -e, --env <strings...>            environment variable(s) set as string (example: "HELLO=Dotenvx") (default: [])
+  -f, --env-file <paths...>         path(s) to your env file(s) (default: [])
+  -fv, --env-vault-file <paths...>  path(s) to your .env.vault file(s) (default: [])
+  -o, --overload                    override existing env variables
+  --convention <name>               load a .env convention (available conventions: ['nextjs'])
+  -h, --help                        display help for command
+
+Examples:
+
+  $ dotenvx run -- npm run dev
+  $ dotenvx run -- flask --app index run
+  $ dotenvx run -- php artisan serve
+  $ dotenvx run -- bin/rails s
+
+Try it:
+
+  $ echo "HELLO=Dotenvx" > .env
+  $ echo "console.log('Hello ' + process.env.HELLO)" > index.js
+
+  $ dotenvx run -- node index.js
+  [dotenvx@1.X.X] injecting env (1) from .env
+  Hello Dotenvx
+```
+
+</details>
+<details><summary>`--version`</summary><br>
+
+Check current version of `dotenvx`.
+
+```sh
+$ dotenvx --version
+X.X.X
+```
+
+</details>
+
+### Extensions 🔌
+
+CLI extensions.
+
+<details><summary>`ext genexample`</summary><br>
+
+In one command, generate a `.env.example` file from your current `.env` file contents.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+
+$ dotenvx ext genexample
+▣ generated (.env.example)
+```
+
+```ini
+# .env.example
+HELLO=""
+```
+
+</details>
+<details><summary>`ext genexample -f`</summary><br>
+
+Pass multiple `.env` files to generate your `.env.example` file from the combination of their contents.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ echo "DB_HOST=example.com" > .env.production
+
+$ dotenvx ext genexample -f .env -f .env.production
+▣ generated (.env.example)
+```
+
+```ini
+# .env.example
+HELLO=""
+DB_HOST=""
+```
+
+</details>
+<details><summary>`ext genexample directory`</summary><br>
+
+Generate a `.env.example` file inside the specified directory. Useful for monorepos.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ mkdir -p apps/backend
+$ echo "HELLO=Backend" > apps/backend/.env
+
+$ dotenvx ext genexample apps/backend
+▣ generated (.env.example)
+```
+
+```ini
+# apps/backend/.env.example
+HELLO=""
+```
+
+</details>
+<details><summary>`ext gitignore`</summary><br>
+
+Gitignore your `.env` files.
+
+```sh
+$ dotenvx ext gitignore
+▣ ignored .env* (.gitignore)
+```
+
+</details>
+<details><summary>`ext gitignore --pattern`</summary><br>
+
+Gitignore specific pattern(s) of `.env` files.
+
+```sh
+$ dotenvx ext gitignore --pattern .env.keys
+▣ ignored .env.keys (.gitignore)
+```
+
+</details>
+<details><summary>`ext precommit`</summary><br>
+
+Prevent `.env` files from being committed to code.
+
+```sh
+$ dotenvx ext precommit
+▣ .env files (1) protected (encrypted or gitignored)
+```
+
+</details>
+<details><summary>`ext precommit --install`</summary><br>
+
+Install a shell script to `.git/hooks/pre-commit` to prevent accidentally committing any `.env` files to source control.
+
+```sh
+$ dotenvx ext precommit --install
+▣ dotenvx ext precommit installed [.git/hooks/pre-commit]
+```
+
+</details>
+<details><summary>`ext precommit directory`</summary><br>
+
+Prevent `.env` files from being committed to code inside a specified path to a directory.
+
+```sh
+$ echo "HELLO=Dotenvx" > .env
+$ mkdir -p apps/backend
+$ echo "HELLO=Backend" > apps/backend/.env
+
+$ dotenvx ext precommit apps/backend
+▣ apps/backend/.env not protected (encrypted or gitignored)
+```
+
+</details>
+<details><summary>`ext prebuild`</summary><br>
+
+Prevent `.env` files from being built into your docker containers.
+
+Add it to your `Dockerfile`.
+
+```Containerfile
+# Install via script
+RUN curl -fsS https://dotenvx.sh | sh
+
+# Or copy binary from official image
+COPY --from=dotenv/dotenvx:latest /usr/local/bin/dotenvx /bin/local/bin
+
+# ... orther container commands
+
+RUN dotenvx ext prebuild
+CMD ["/usr/local/bin/dotenvx", "run", "--", "node", "index.js"]
+```
+
+</details>
+<details><summary>`ext prebuild directory`</summary><br>
+
+Prevent `.env` files from being built into your docker containers inside a specified path to a directory.
+
+Add it to your `Dockerfile`.
+
+```Containerfile
+# Install via script
+RUN curl -fsS https://dotenvx.sh | sh
+
+# Or copy binary from official image
+COPY --from=dotenv/dotenvx:latest /usr/local/bin/dotenvx /bin/local/bin
+
+# ... orther container commands
+
+RUN dotenvx ext prebuild apps/backend
+CMD ["/usr/local/bin/dotenvx", "run", "--", "node", "apps/backend/index.js"]
+```
+
+</details>
+<details><summary>`ext scan`</summary><br>
+
+Scan for leaked secrets.
+
+```sh
+$ dotenvx ext scan
+100 commits scanned.
+no leaks found
+```
+
+Uses [gitleaks](https://gitleaks.io) under the hood.
+
+</details>
+
+### Library 📦
+
+Use dotenvx directly in code.
+
+<details><summary>`config()`</summary><br>
+
+Use directly in node.js code.
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config()
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+[dotenvx@1.X.X] injecting env (1) from .env
+Hello Dotenvx
+```
+
+It defaults to looking for a `.env` file.
+
+</details>
+<details><summary>`config(path: ['.env.local', '.env'])` - multiple files</summary><br>
+
+Specify path(s) to multiple .env files.
+
+```ini
+# .env.local
+HELLO="Me"
+```
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env.local', '.env']})
+
+// esm
+// import dotenvx from "@dotenvx/dotenvx";
+// dotenvx.config({path: ['.env.local', '.env']});
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local, .env
+Hello Me
+```
+
+</details>
+<details><summary>`config(overload: true)` - overload</summary><br>
+
+Use `overload` to overwrite the prior set value.
+
+```ini
+# .env.local
+HELLO="Me"
+```
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env.local', '.env'], overload: true})
+
+// esm
+// import dotenvx from "@dotenvx/dotenvx";
+// dotenvx.config({path: ['.env.local', '.env'], overload: true});
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+[dotenvx@1.X.X] injecting env (1) from .env.local, .env
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`config(quiet: true)` - quiet</summary><br>
+
+Suppress all output (except errors).
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env.missing', '.env'], quiet: true})
+
+// esm
+// import dotenvx from "@dotenvx/dotenvx";
+// dotenvx.config({path: ['.env.missing', '.env'], quiet: true});
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+Error: [MISSING_ENV_FILE] missing .env.missing file (/path/to/.env.missing)
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`config(strict: true)` - strict</summary><br>
+
+Exit with code `1` if any errors are encountered - like a missing .env file or decryption failure.
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env.missing', '.env'], strict: true})
+
+// esm
+// import dotenvx from "@dotenvx/dotenvx";
+// dotenvx.config({path: ['.env.missing', '.env'], strict: true});
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+Error: [MISSING_ENV_FILE] missing .env.missing file (/path/to/.env.missing)
+```
+
+</details>
+<details><summary>`config(ignore:)` - ignore</summary><br>
+
+Use `ignore` to suppress specific errors like `MISSING_ENV_FILE`.
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env.missing', '.env'], ignore: ['MISSING_ENV_FILE']})
+
+// esm
+// import dotenvx from "@dotenvx/dotenvx";
+// dotenvx.config({path: ['.env.missing', '.env'], ignore: ['MISSING_ENV_FILE']});
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ node index.js
+[dotenvx@1.X.X] injecting env (1) from .env
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`config(envKeysFile:)` - envKeysFile</summary><br>
+
+Use `envKeysFile` to customize the path to your `.env.keys` file. This is useful with monorepos.
+
+```ini
+# .env
+HELLO="Dotenvx"
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({path: ['.env'], envKeysFile: '../../.env.keys'})
+```
+
+</details>
+<details><summary>`config(convention:)` - convention</summary><br>
+
+Set a convention when using `dotenvx.config()`. This allows you to use the same file loading order as the CLI without needing to specify each file individually.
+
+```sh
+# Setup environment files
+$ echo "HELLO=development local" > .env.development.local
+$ echo "HELLO=local" > .env.local
+$ echo "HELLO=development" > .env.development
+$ echo "HELLO=env" > .env
+```
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({ convention: 'nextjs' })
+
+console.log(`Hello ${process.env.HELLO}`)
+```
+
+```sh
+$ NODE_ENV=development node index.js
+[dotenvx@1.28.0] injecting env (1) from .env.development.local, .env.local, .env.development, .env
+Hello development local
+```
+
+This is equivalent to using `--convention=nextjs` with the CLI:
+
+```sh
+$ dotenvx run --convention=nextjs -- node index.js
+```
+
+</details>
+<details><summary>`config(noArmor:)` - noArmor</summary><br>
+
+Turn off [Dotenvx Armor ⛨](https://dotenvx.com/armor) features.
+
+```js
+// index.js
+require('@dotenvx/dotenvx').config({noArmor: true})
+```
+
+`noVlt` and `noOps` are deprecated aliases.
+
+</details>
+<details><summary>`parse(src)`</summary><br>
+
+Parse a `.env` string directly in node.js code.
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+const src = 'HELLO=Dotenvx'
+const parsed = dotenvx.parse(src)
+console.log(`Hello ${parsed.HELLO}`)
+```
+
+```sh
+$ node index.js
+Hello Dotenvx
+```
+
+</details>
+<details><summary>`parse(src, {processEnv:})`</summary><br>
+
+Sometimes, you want to run `parse` without it accessing `process.env`. (You can pass a fake processEnv this way as well - sometimes useful.)
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+const src = 'USER=Me'
+const parsed = dotenvx.parse(src, { processEnv: {} })
+console.log(`Hello ${parsed.USER}`)
+```
+
+```sh
+$ node index.js
+Hello Me
+```
+
+</details>
+<details><summary>`parse(src, {privateKey:})`</summary><br>
+
+Decrypt an encrypted `.env` string with `privateKey`.
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+const src = 'HELLO="encrypted:BE9Y7LKANx77X1pv1HnEoil93fPa5c9rpL/1ps48uaRT9zM8VR6mHx9yM+HktKdsPGIZELuZ7rr2mn1gScsmWitppAgE/1lVprNYBCqiYeaTcKXjDUXU5LfsEsflnAsDhT/kWG1l"'
+const parsed = dotenvx.parse(src, { privateKey: 'a4547dcd9d3429615a3649bb79e87edb62ee6a74b007075e9141ae44f5fb412c' })
+console.log(`Hello ${parsed.HELLO}`)
+```
+
+```sh
+$ node index.js
+Hello Dotenvx
+```
+</details>
+<details><summary>`set(KEY, value)`</summary><br>
+
+Programmatically set an environment variable. 
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+dotenvx.set('HELLO', 'Dotenvx', { path: '.env' })
+```
+
+</details>
+<details><summary>`set(KEY, value, {plain:})`</summary><br>
+
+Programmatically set a plaintext environment variable.
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+dotenvx.set('HELLO', 'Dotenvx', { plain: true })
+```
+
+</details>
+<details><summary>`get(KEY)` - <i>Decryption at Access</i></summary><br>
+
+Programmatically get an environment variable at access/runtime.
+
+```js
+// index.js
+const dotenvx = require('@dotenvx/dotenvx')
+const decryptedValue = dotenvx.get('HELLO')
+console.log(decryptedValue)
+```
+
+This is known as *Decryption at Access* and is written about in [the whitepaper](https://dotenvx.com/dotenvx.pdf).
+
+</details>
+
+&nbsp;
+
+## Armor ⛨
+
+[![dotenvx-armor](https://dotenvx.com/dotenvx-armor-banner.png?v2)](https://dotenvx.com/armor)
+
+```
+⛨ ARMORED KEYS: Harden your private keys.
+⮕ install [curl -sfS https://dotenvx.sh/armor | sh]
+⮕ then run [dotenvx armor login]
+```
+
+[Learn more](https://dotenvx.com/armor)
+
+&nbsp;
+
+## Whitepaper
+
+> **Dotenvx: Reducing Secrets Risk with Cryptographic Separation**
+>
+> Abstract. An ideal secrets solution would not only centralize secrets but also contain the fallout of a breach. While secrets managers offer centralized storage and distribution, their design creates a large blast radius, risking exposure of thousands or even millions of secrets. We propose a solution that reduces the blast radius by splitting secrets management into two distinct components: an encrypted secrets file and a separate decryption key.
+>
+> ...
+>
+> [Read the whitepaper](https://dotenvx.com/dotenvx.pdf)
+
+&nbsp;
+
+## Guides
+
+> Go deeper with `dotenvx` – detailed framework and platform guides.
+>
+
+* [Languages](https://dotenvx.com/docs#languages)
+  * [Node.js](https://dotenvx.com/docs/languages/nodejs)
+  * [Python](https://dotenvx.com/docs/languages/python)
+  * [Ruby](https://dotenvx.com/docs/languages/ruby)
+  * [Go](https://dotenvx.com/docs/languages/go)
+  * [PHP](https://dotenvx.com/docs/languages/php)
+  * [Rust](https://dotenvx.com/docs/languages/rust)
+* [Frameworks](https://dotenvx.com/docs#frameworks)
+  * [Astro](https://dotenvx.com/docs/frameworks/astro)
+  * [Express](https://dotenvx.com/docs/frameworks/express)
+  * [Next](https://dotenvx.com/docs/frameworks/next)
+  * [Remix](https://dotenvx.com/docs/frameworks/remix)
+  * [Flask](https://dotenvx.com/docs/frameworks/flask)
+  * [Sinatra](https://dotenvx.com/docs/frameworks/sinatra)
+  * [Rocket](https://dotenvx.com/docs/frameworks/rocket)
+* [Platforms](https://dotenvx.com/docs#platforms)
+  * [Digital Ocean](https://dotenvx.com/docs/platforms/digital-ocean)
+  * [Docker](https://dotenvx.com/docs/platforms/docker)
+  * [Fly](https://dotenvx.com/docs/platforms/fly)
+  * [Heroku](https://dotenvx.com/docs/platforms/heroku)
+  * [Netlify](https://dotenvx.com/docs/platforms/netlify)
+  * [Vercel](https://dotenvx.com/docs/platforms/vercel)
+  * [Railway](https://dotenvx.com/docs/platforms/railway)
+  * [Render](https://dotenvx.com/docs/platforms/render)
+* [CI/CDs](https://dotenvx.com/docs#cis)
+  * [GitHub Actions](https://dotenvx.com/docs/cis/github-actions)
+* [Background Jobs](https://dotenvx.com/docs#background-jobs)
+  * [Trigger.dev](https://dotenvx.com/docs/background-jobs/triggerdotdev)
+* [Package Managers](https://dotenvx.com/docs#package-managers)
+  * [NPM](https://dotenvx.com/docs/package-managers/npm)
+  * [PNPM](https://dotenvx.com/docs/package-managers/pnpm)
+* [Process Managers](https://dotenvx.com/docs#process-managers)
+  * [PM2](https://dotenvx.com/docs/process-managers/pm2)
+* [Monorepos](https://dotenvx.com/docs#monorepos)
+  * [Nx](https://dotenvx.com/docs/monorepos/nx)
+  * [Turborepo](https://dotenvx.com/docs/monorepos/turborepo)
+* [Concepts](https://dotenvx.com/docs#concepts)
+  * [.env](https://dotenvx.com/docs/env-file)
+  * [.env.keys](https://dotenvx.com/docs/env-keys-file)
+
+&nbsp;
+
+## FAQ
+
+#### How does encryption work?
+
+Dotenvx uses Elliptic Curve Integrated Encryption Scheme (ECIES) to encrypt each secret with a unique ephemeral key, while ensuring it can be decrypted using a long-term private key.
+
+When you initialize encryption, a DOTENV_PUBLIC_KEY (encryption key) and DOTENV_PRIVATE_KEY (decryption key) are generated. The DOTENV_PUBLIC_KEY is used to encrypt secrets, and the DOTENV_PRIVATE_KEY is securely stored in your cloud secrets manager or .env.keys file.
+
+Your encrypted .env file is then safely committed to code. Even if the file is exposed, secrets remain protected since decryption requires the separate DOTENV_PRIVATE_KEY, which is never stored alongside it. Read [the whitepaper](https://dotenvx.com/dotenvx.pdf?v=README) for more details.
+
+#### Is it safe to commit an encrypted .env file to code?
+
+Yes. Dotenvx encrypts secrets using AES-256 with ephemeral keys, ensuring that even if the encrypted .env file is exposed, its contents remain secure. The encryption keys themselves are protected using Secp256k1 elliptic curve cryptography, which is widely used for secure key exchange in technologies like Bitcoin.
+
+This means that every secret in the .env file is encrypted with a unique AES-256 key, and that key is further encrypted using a public key (Secp256k1). Even if an attacker obtains the encrypted .env file, they would still need the corresponding private key—stored separately in a secrets manager—to decrypt anything.
+
+Breaking this encryption would require brute-forcing both AES-256 and elliptic curve cryptography, which is computationally infeasible with current technology. Read [the whitepaper](https://dotenvx.com/dotenvx.pdf?v=README) for more details.
+
+#### Why am I getting the error `node: .env: not found`?
+
+You are using Node 20 or greater and it adds a differing implementation of `--env-file` flag support. Rather than warn on a missing `.env` file (like dotenv has historically done), it raises an error: `node: .env: not found`.
+
+This fix is easy. Replace `--env-file` with `-f`.
+
+```bash
+# from this:
+./node_modules/.bin/dotenvx run --env-file .env -- yourcommand
+# to this:
+./node_modules/.bin/dotenvx run -f .env -- yourcommand
+```
+
+[more context](https://github.com/dotenvx/dotenvx/issues/131)
+
+&nbsp;
+
+## Contributing
+
+You can fork this repo and create [pull requests](https://github.com/dotenvx/dotenvx/pulls) or if you have questions or feedback:
+
+* [github.com/dotenvx/dotenvx](https://github.com/dotenvx/dotenvx/issues) - bugs and discussions
+* [@dotenvx 𝕏](https://x.com/dotenvx) (DMs are open)