NEXT_PUBLIC_APP_URL=https://myapp.com API_URL=https://api.myapp.com
You named it .env.local.production by mistake, or you changed a variable and didn't restart your dev server or rebuild your project.
# .env.example NEXT_PUBLIC_APP_URL=https://your-app-url.com API_KEY=your-api-key-here DATABASE_URL=your-database-url-here
Public configurations, safe URLs, non-sensitive build flags. Private API keys, local database URIs, secret tokens. Sets the baseline production configuration defaults. .env.local.production
You want to run your application locally (e.g., next start or vite preview ) but want to use the live API endpoints, production database keys, or analytics tokens 1.2.5 .
Sensitive production secrets used during local production testing or CI/CD builds
: Most frameworks load environment files in a specific order; .env.local.production will typically take precedence over .env.production and .env . NEXT_PUBLIC_APP_URL=https://myapp
Are you using environment files in a unique way? Let me know in the comments!
: Specifies a local override . This file is machine-specific and is designed to bypass the default, committed environment settings.
Let's say you are building a Next.js app. Sets the baseline production configuration defaults
export const env = databaseUrl: requireEnv('DATABASE_URL'), stripeSecretKey: requireEnv('STRIPE_SECRET_KEY'), // ... other required variables ;
The framework loads .env.local first (lower priority) and then .env.production.local (higher priority). Variables from the production-local file will win.