How to Manage App Configuration Cleanly Across Dev, Staging, and Production

Applications typically run across multiple environments — local, staging, and production — each requiring different database URLs, credentials, and service addresses. Hardcoding these values directly into source code ties deployment-specific details to the application itself, making portability difficult. A cleaner approach is to have the application declare what configuration it needs while the surrounding environment supplies the appropriate values at runtime. Operating systems support this through environment variables, which Node.js applications can access via process.env, regardless of whether values are injected by a shell, Docker, or Kubernetes. This pattern cleanly separates application logic from environment-specific configuration, allowing the same build to run consistently across all deployment targets.