Skip to main content

Starter Templates

ENV Manager Pro ships with seven framework-specific .env templates. Each template includes the environment variables most commonly needed by that framework, with descriptive placeholder values.

Using a Template​

Click 📦 New from Template in the Pro Tools panel, or run ENV Manager: New .env from Template.

  1. Choose your framework from the quick pick list
  2. Enter a filename (e.g. .env.local, .env)
  3. The file is created in your workspace root and opened in the editor

Available Templates​

Next.js​

File: .env.local

# App
NEXT_PUBLIC_APP_URL=http://localhost:3000
NEXT_PUBLIC_APP_NAME=My Next App

# Auth (NextAuth.js)
NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET=your_secret_here

# Database
DATABASE_URL=postgresql://postgres:password@localhost:5432/mydb

# APIs
OPENAI_API_KEY=your_secret_here
STRIPE_SECRET_KEY=your_secret_here
STRIPE_PUBLISHABLE_KEY=your_value_here

# Email
SENDGRID_API_KEY=your_secret_here

Express.js​

File: .env

Includes: PORT, NODE_ENV, DATABASE_URL, JWT_SECRET, CORS_ORIGIN, REDIS_URL, LOG_LEVEL, API_KEY

Django​

File: .env

Includes: DJANGO_SECRET_KEY, DEBUG, ALLOWED_HOSTS, DATABASE_URL, REDIS_URL, EMAIL_HOST, SENTRY_DSN, AWS_ACCESS_KEY_ID, AWS_S3_BUCKET_NAME

Laravel​

File: .env

Includes: APP_NAME, APP_ENV, APP_KEY, APP_DEBUG, APP_URL, DB_CONNECTION, DB_HOST, DB_DATABASE, CACHE_DRIVER, QUEUE_CONNECTION, MAIL_MAILER, AWS_ACCESS_KEY_ID

FastAPI​

File: .env

Includes: APP_NAME, APP_ENV, DATABASE_URL, SECRET_KEY, ACCESS_TOKEN_EXPIRE_MINUTES, REDIS_URL, OPENAI_API_KEY, AWS_ACCESS_KEY_ID, SENTRY_DSN

React + Vite​

File: .env

Includes: VITE_APP_NAME, VITE_API_BASE_URL, VITE_AUTH0_DOMAIN, VITE_AUTH0_CLIENT_ID, VITE_STRIPE_PUBLISHABLE_KEY, VITE_SENTRY_DSN, VITE_GOOGLE_ANALYTICS_ID

NestJS​

File: .env

Includes: PORT, NODE_ENV, DATABASE_URL, JWT_SECRET, JWT_EXPIRATION, REDIS_HOST, REDIS_PORT, THROTTLE_TTL, THROTTLE_LIMIT, SWAGGER_ENABLED

After Creating from Template​

After the file is created:

  1. Use Smart Suggestions to automatically identify any additional variables needed by packages in your package.json
  2. Fill in the placeholder values with your real secrets
  3. Run Secret Leak Scanner to verify .gitignore covers the new file
  4. Run Generate .env.example to create a shareable example file