Skip to content

Command Line Tools

Wheels get settings

The wheels get settings command displays the current Wheels application settings for your environment. It shows all configuration settings that are active, including defaults and any custom overrides from your configuration files. You can view all settings or filter to see specific ones.

Terminal window
wheels get settings [settingName]
  • settingName - Optional setting name or pattern to filter results. Can be a partial match.
Terminal window
wheels get settings

Shows all active settings for the current environment

Terminal window
wheels get settings cacheQueries

Shows only the cacheQueries setting

Terminal window
wheels get settings cache

Shows all settings containing β€œcache” in their name (e.g., cacheQueries, cachePages, cacheImages)

The command resolves settings in the same order as Wheels:

  1. Default Wheels Settings - Built-in framework defaults
  2. Application Settings - From /config/settings.cfm
  3. Environment Settings - From /config/[environment]/settings.cfm

Each level overrides the previous one, with environment-specific settings having the highest priority.

The command automatically detects the current environment using the same logic as wheels get environment:

  • Checks .env file for WHEELS_ENV
  • Checks system environment variable
  • Checks server.json
  • Defaults to development

The command parses set() function calls in your settings files:

config/settings.cfm
set(dataSourceName="myapp_db");
set(cacheQueries=true);
set(errorEmailAddress="admin@example.com");
Wheels Settings (development environment):
allowConcurrentRequestScope: false
cacheActions: false
cacheCullInterval: 5
cacheCullPercentage: 10
cacheDatabaseSchema: false
cacheFileChecking: false
cacheImages: false
cacheModelConfig: false
cachePages: false
cachePartials: false
cacheQueries: false
cacheRoutes: false
dataSourceName: myapp_db
errorEmailAddress: admin@example.com
showDebugInformation: true
showErrorInformation: true
URLRewriting: partial
Total settings: 17
Terminal window
wheels get settings cache
==================================================
Wheels Settings (development environment)
==================================================
╔═══════════════════════╀═══════╗
β•‘ Setting β”‚ Value β•‘
╠═══════════════════════β•ͺ═══════╣
β•‘ cacheActions β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheControllerConfig β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheCullInterval β”‚ true β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheCullPercentage β”‚ true β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheDatabaseSchema β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheFileChecking β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheImages β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheModelConfig β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cachePages β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cachePartials β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheQueries β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheRoutes β”‚ false β•‘
β•Ÿβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β•’
β•‘ cacheViewConfig β”‚ false β•‘
β•šβ•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•§β•β•β•β•β•β•β•β•
Total settings: 13
Terminal window
wheels get settings dataSourceName
==================================================
Wheels Settings (development environment)
==================================================
╔════════════════╀══════════════╗
β•‘ Setting β”‚ Value β•‘
╠════════════════β•ͺ══════════════╣
β•‘ dataSourceName β”‚ wheelstestdb β•‘
β•šβ•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•§β•β•β•β•β•β•β•β•β•β•β•β•β•β•β•
Total settings: 1
[INFO]: Settings loaded from:
- config/settings.cfm (global defaults)
- config/development/settings.cfm (environment overrides)
[INFO]: Filtered by: 'dataSourceName'
- Showing 1 matching setting(s)
Terminal window
wheels get settings nonexistent
[WARNING]: No settings found matching 'nonexistent'
  • cacheActions - Cache action output
  • cacheQueries - Cache database query results
  • cachePages - Cache entire page output
  • cachePartials - Cache partial/template output
  • cacheImages - Cache generated images
  • cacheRoutes - Cache routing configuration
  • cacheModelConfig - Cache model configurations
  • cacheControllerConfig - Cache controller configurations
  • cacheViewConfig - Cache view configurations
  • cacheDatabaseSchema - Cache database schema information
  • cacheFileChecking - Check for file changes when caching
  • dataSourceName - Primary datasource name
  • useExpandedColumnAliases - Use expanded column aliases in queries
  • useTimestampsOnDeletedColumn - Add timestamps to soft-deleted records
  • migratorTableName - Table name for migration versions
  • showDebugInformation - Display debug information
  • showErrorInformation - Display error details
  • sendEmailOnError - Send email notifications on errors
  • errorEmailAddress - Email address for error notifications
  • errorEmailServer - SMTP server for error emails
  • errorEmailSubject - Subject line for error emails
  • includeErrorInEmailSubject - Include error details in email subject
  • URLRewriting - URL rewriting mode (none, partial, full)
  • overwritePlugins - Allow plugin overwrites
  • deletePluginDirectories - Delete plugin directories on uninstall
  • loadIncompatiblePlugins - Load plugins with version mismatches
Terminal window
# Check development settings
WHEELS_ENV=development wheels get settings cache
# Check production settings
WHEELS_ENV=production wheels get settings cache
Terminal window
wheels get settings dataSourceName
Terminal window
wheels get settings cache
Terminal window
# See all current settings
wheels get settings
# Check specific problematic setting
wheels get settings showDebugInformation
Terminal window
# Verify production settings
WHEELS_ENV=production wheels get settings
config/settings.cfm
set(dataSourceName="myapp");
set(URLRewriting="partial");
set(errorEmailAddress="admin@myapp.com");
config/production/settings.cfm
set(cacheQueries=true);
set(cachePages=true);
set(cachePartials=true);
set(showDebugInformation=false);
set(showErrorInformation=false);
set(sendEmailOnError=true);
config/development/settings.cfm
set(cacheQueries=false);
set(showDebugInformation=true);
set(showErrorInformation=true);
set(sendEmailOnError=false);

The command correctly interprets different data types:

set(cacheQueries=true);
set(showDebugInformation=false);
set(cacheCullInterval=5);
set(cacheCullPercentage=10);
set(dataSourceName="myapp_db");
set(errorEmailAddress="admin@example.com");

Arrays and structs are displayed with summary information:

complexSetting: [array with 5 items]
structSetting: {3 items}

The command will show an error if:

  • Not run from a Wheels application directory
  • Settings files cannot be read
  • Settings files contain syntax errors
Error: This command must be run from a Wheels application directory
Error reading settings: [specific error message]
Details: [additional error details if available]
  1. Environment-Specific Configs - Keep environment-specific settings in separate files (/config/[environment]/settings.cfm)

  2. Document Custom Settings - Comment your custom settings in the configuration files

  3. Use Consistent Naming - Follow Wheels naming conventions for custom settings

  4. Verify Before Deployment - Always check settings for the target environment before deploying

  5. Sensitive Data - Keep sensitive settings (API keys, passwords) in environment variables or .env files

Works well with other Wheels CLI commands:

Terminal window
# Check environment, then settings
wheels get environment
wheels get settings
# Verify cache settings before clearing cache
wheels get settings cache
wheels clear cache
# Check database settings before running migrations
wheels get settings dataSourceName
wheels db migrate
  • Setting names are case-insensitive when filtering
  • The filter matches any part of the setting name
  • Settings are displayed in alphabetical order
  • Boolean values display as true or false
  • Complex values (arrays, structs) show a summary
  • The command shows which environment’s settings are being displayed
  1. Check which environment is active: wheels get environment
  2. Verify the settings file exists in the correct location
  3. Check for syntax errors in your settings files
  4. Ensure settings use the correct set() function syntax

If expected settings are missing:

  • Verify they’re defined using set() function
  • Check file paths: /config/settings.cfm and /config/[environment]/settings.cfm
  • Ensure no syntax errors prevent parsing
  • Remember the filter is case-insensitive
  • The filter matches any part of the setting name
  • Use more specific terms for precise filtering
  • The command parses settings files statically and may not capture all dynamic settings
  • Complex CFML expressions in settings may not be fully evaluated
  • Settings defined outside of set() function calls may not be detected
  • Runtime settings modifications are not reflected