Environment-Specific Configuration in ColdFusion: Dev, Staging, and Production Done Right

The right way to handle per-environment configuration in ColdFusion is to keep configuration out of your code and out of the ColdFusion Administrator, and put it in environment variables — then read it through a single, centralized configuration component. In practice that means: detect the current environment from an env var (ENVIRONMENT=production) rather than by sniffing hostnames; read values with System.getenv() (real-time) rather than server.os.environment (a snapshot taken at server start that does not refresh when you add a variable); never read config from the CGI scope (those aren't OS environment variables and clients can spoof them); manage ColdFusion Administrator settings — datasources, mail, memory — as version-controlled code with CFConfig and its cfconfig_ environment variables instead of clicking through the UI; and centralize every environment lookup in one Config.cfc so there's a single source of truth with fallbacks and validation. The litmus test for whether you've done it right: could you open-source your repository right now without leaking a single credential? If not, config is still living in your code. This guide shows the complete pattern.
Read More