Feature

Personal Environment Variables

Control personal environment variables that only you can see.

🛡 Layer 3 Feature

Personal Environment Variables are a wonderful hidden feature of Dotenv.

How They Work

  1. Place # personal.dotenv.org in your .env file.
  2. Any environment variables after that comment become personal environment variables.
  3. Only you can see them.

Example

DB_HOST=localhost
DB_PASSWORD=pa$$word
ENCRYPT_PUBLIC_KEY=5daef8d0b8c62f9569a634c88574cdd0
GATSBY_API_URL=http://localhost:3000/gatsby
MAILCHIMP_API_USERNAME=d3a5f1d9f215941181752a7f0bda5380
S3_KEY=cd89a34bcd76
SIGN_PUBLIC_KEY=84a8cfc121cb6b517f7c11c92cad2cc7
STRIPE_KEY=scr_a34bd7c37abc
STRIPE_PUBLIC_KEY="pub_z17ab3d3741a"

# personal.dotenv.org
DB_HOST=0.0.0.0
DB_PASSWORD=password

Use Cases

Sometimes developers maintain a different local database configuration to their team members. Sometimes they are developing a new feature with a new environment variable that is not quite ready for the entire team to know about. There are a number of developer flow reasons to make use of Personal Environment Variables.

Ready to get started?

Join millions of developers that already trust and use Dotenv.

No credit card required
Dotenv for
  • Agencies
  • Startups
  • Enterprises
  • Bootstrapped Startups
  • Side Projects
  • Developers

💛 Est. 2013