Blog

ColdBox Free Tip 1: Environment Variables In The Config

Maria Jose Herrera September 19, 2024

Spread the word

Maria Jose Herrera

September 19, 2024

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!

ColdBox Book

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

Add Your Comment

Recent Entries

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

At Ortus Solutions, we’ve always been at the forefront of innovation in the ColdFusion ecosystem. From pioneering modern ColdFusion practices to developing cutting-edge tools and frameworks, we’ve been passionate to help and sup[port the community into shaping the future of web development.That’s why we decided to build BoxLang, our new JVM programming language that not only builds on the strengths of ColdFusion but takes modern software development to the next level.

Maria Jose Herrera
Maria Jose Herrera
December 23, 2024
Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

Why BoxLang When You Have Kotlin, Groovy, Scala, and more…

As we approach a stable release of BoxLang and our continued marketing reaches more folks, many have asked about its purpose. Why create a new language when the JVM ecosystem already includes established languages like Kotlin, Groovy, and Scala, to name a few.

Luis Majano
Luis Majano
December 18, 2024