Blog

ColdBox Free Tip 1: Environment Variables In The Config

Victor Campos August 25, 2025

Spread the word

Victor Campos

August 25, 2025

Spread the word


Share your thoughts

1/10 FREE ColdBox Tips and Tricks - Book: 102 ColdBox Tips and Tricks!

Welcome to the first of 10 FREE tips and tricks in our "102 ColdBox Tips and Tricks" Book! In this post, we’ll show you how to easily access system environment variables within your ColdBox configuration files, making your app setup smoother and more flexible!

More Tips and Tricks

Using getSystemSetting() Method!

When working within a ColdBox.cfc or a ModuleConfig.cfc, you can leverage the getSystemSetting() method to retrieve system environment variables. Here’s how it works:

appName = getSystemSetting( "APPNAME", "ContentBox Modular CMS" )
tier = getSystemSetting( "ENVIRONMENT", "PRODUCTION" )
  • First Parameter: Name of the environment variable.
  • Second Parameter: A default value, in case the variable is not found.
  • Please note that all environment variables are strings

ColdBox Book

Order of Lookup

The getSystemSetting() method follows a specific order when looking for the environment variable:

  1. Java system properties
  2. System environment variables

Need a Specific Value?

  • If you only need a Java system property, use the getSystemProperty() method.
  • If you only need a system environment variable, use the getEnv() method.

Using these methods, you can manage your environment configurations more efficiently, ensuring that your ColdBox applications are always correctly set up across different environments.

.env Convention

If you are running your ColdBox applications with CommandBox, you have the extra benefit of having an .env file in the root of your application. CommandBox will read it and seed it into the engine for you upon startup so you can use those as environment variables. Here is a sample .env file:

# ColdBox Name and Environment
APPNAME=ColdBox
ENVIRONMENT=development

# Database Information
DB_CONNECTIONSTRING=jdbc:mysql: //127.0.0.1:3306/coldbox?useSSL=false&useUnicode=true&characterEncoding=UTF-8&serverTimezone=UTC&useLegacyDatetimeCode=true&allowPublicKeyRetrieval=true
DB_CLASS=com.mysql.jdbc.Driver
DB_BUNDLENAME=com.mysql.cj
DB_BUNDLEVERSION=8.0.30
DB_DRIVER=MySQL
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=coldbox
DB_USER=root
DB_PASSWORD=

# JWT Information
JWT_SECRET=

# S3 Information
S3_ACCESS_KEY=
S3_SECRET_KEY=
S3_REGION=us-east-1
S3_DOMAIN=amazonaws.com

Learn More ColdBox Tips and Tricks

Stay tuned for more ColdBox tips in our ongoing series. if you want to learn more than 10 free tips and tricks make sure to get your “ColdBox 102 tips and tricks book” We have a variety of formats you can choose from.

Get your Copy

Join the Ortus Community

Be part of the movement shaping the future of web development. Stay connected and receive the latest updates on**, product launches, tool updates, promo services and much more.**

Subscribe to our newsletter for exclusive content.

Follow Us on Social media and don’t miss any news and updates:

Add Your Comment

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025