Command Line Tools
Wheels get settings
Wheels get settings
Section titled “Wheels get settings”Overview
Section titled “Overview”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.
Command Syntax
Section titled “Command Syntax”wheels get settings [settingName]Parameters
Section titled “Parameters”Optional Parameters
Section titled “Optional Parameters”settingName- Optional setting name or pattern to filter results. Can be a partial match.
Basic Usage Examples
Section titled “Basic Usage Examples”Display All Settings
Section titled “Display All Settings”wheels get settingsShows all active settings for the current environment
Filter Specific Setting
Section titled “Filter Specific Setting”wheels get settings cacheQueriesShows only the cacheQueries setting
Filter by Pattern
Section titled “Filter by Pattern”wheels get settings cacheShows all settings containing “cache” in their name (e.g., cacheQueries, cachePages, cacheImages)
How It Works
Section titled “How It Works”Settings Resolution Order
Section titled “Settings Resolution Order”The command resolves settings in the same order as Wheels:
- Default Wheels Settings - Built-in framework defaults
- Application Settings - From
/config/settings.cfm - Environment Settings - From
/config/[environment]/settings.cfm
Each level overrides the previous one, with environment-specific settings having the highest priority.
Environment Detection
Section titled “Environment Detection”The command automatically detects the current environment using the same logic as wheels get environment:
- Checks
.envfile forWHEELS_ENV - Checks system environment variable
- Checks
server.json - Defaults to
development
Settings Parsing
Section titled “Settings Parsing”The command parses set() function calls in your settings files:
set(dataSourceName="myapp_db");set(cacheQueries=true);set(errorEmailAddress="admin@example.com");Output Examples
Section titled “Output Examples”All Settings Display
Section titled “All Settings Display”Wheels Settings (development environment):
allowConcurrentRequestScope: falsecacheActions: falsecacheCullInterval: 5cacheCullPercentage: 10cacheDatabaseSchema: falsecacheFileChecking: falsecacheImages: falsecacheModelConfig: falsecachePages: falsecachePartials: falsecacheQueries: falsecacheRoutes: falsedataSourceName: myapp_dberrorEmailAddress: admin@example.comshowDebugInformation: trueshowErrorInformation: trueURLRewriting: partial
Total settings: 17Filtered Settings Display
Section titled “Filtered Settings Display”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: 13Single Setting Display
Section titled “Single Setting Display”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)No Matches Found
Section titled “No Matches Found”wheels get settings nonexistent[WARNING]: No settings found matching 'nonexistent'Common Wheels Settings
Section titled “Common Wheels Settings”Caching Settings
Section titled “Caching Settings”cacheActions- Cache action outputcacheQueries- Cache database query resultscachePages- Cache entire page outputcachePartials- Cache partial/template outputcacheImages- Cache generated imagescacheRoutes- Cache routing configurationcacheModelConfig- Cache model configurationscacheControllerConfig- Cache controller configurationscacheViewConfig- Cache view configurationscacheDatabaseSchema- Cache database schema informationcacheFileChecking- Check for file changes when caching
Database Settings
Section titled “Database Settings”dataSourceName- Primary datasource nameuseExpandedColumnAliases- Use expanded column aliases in queriesuseTimestampsOnDeletedColumn- Add timestamps to soft-deleted recordsmigratorTableName- Table name for migration versions
Error Handling Settings
Section titled “Error Handling Settings”showDebugInformation- Display debug informationshowErrorInformation- Display error detailssendEmailOnError- Send email notifications on errorserrorEmailAddress- Email address for error notificationserrorEmailServer- SMTP server for error emailserrorEmailSubject- Subject line for error emailsincludeErrorInEmailSubject- Include error details in email subject
URL Settings
Section titled “URL Settings”URLRewriting- URL rewriting mode (none,partial,full)
Plugin Settings
Section titled “Plugin Settings”overwritePlugins- Allow plugin overwritesdeletePluginDirectories- Delete plugin directories on uninstallloadIncompatiblePlugins- Load plugins with version mismatches
Common Use Cases
Section titled “Common Use Cases”Development vs Production Comparison
Section titled “Development vs Production Comparison”# Check development settingsWHEELS_ENV=development wheels get settings cache
# Check production settingsWHEELS_ENV=production wheels get settings cacheVerify Database Configuration
Section titled “Verify Database Configuration”wheels get settings dataSourceNameCheck All Caching Settings
Section titled “Check All Caching Settings”wheels get settings cacheDebugging Configuration Issues
Section titled “Debugging Configuration Issues”# See all current settingswheels get settings
# Check specific problematic settingwheels get settings showDebugInformationPre-deployment Verification
Section titled “Pre-deployment Verification”# Verify production settingsWHEELS_ENV=production wheels get settingsSettings File Examples
Section titled “Settings File Examples”Basic Application Settings
Section titled “Basic Application Settings”set(dataSourceName="myapp");set(URLRewriting="partial");set(errorEmailAddress="admin@myapp.com");Environment-Specific Settings
Section titled “Environment-Specific Settings”set(cacheQueries=true);set(cachePages=true);set(cachePartials=true);set(showDebugInformation=false);set(showErrorInformation=false);set(sendEmailOnError=true);set(cacheQueries=false);set(showDebugInformation=true);set(showErrorInformation=true);set(sendEmailOnError=false);Data Type Support
Section titled “Data Type Support”The command correctly interprets different data types:
Boolean Values
Section titled “Boolean Values”set(cacheQueries=true);set(showDebugInformation=false);Numeric Values
Section titled “Numeric Values”set(cacheCullInterval=5);set(cacheCullPercentage=10);String Values
Section titled “String Values”set(dataSourceName="myapp_db");set(errorEmailAddress="admin@example.com");Complex Values
Section titled “Complex Values”Arrays and structs are displayed with summary information:
complexSetting: [array with 5 items]structSetting: {3 items}Error Handling
Section titled “Error Handling”The command will show an error if:
- Not run from a Wheels application directory
- Settings files cannot be read
- Settings files contain syntax errors
Not a Wheels Application
Section titled “Not a Wheels Application”Error: This command must be run from a Wheels application directoryRead Error
Section titled “Read Error”Error reading settings: [specific error message]Details: [additional error details if available]Best Practices
Section titled “Best Practices”-
Environment-Specific Configs - Keep environment-specific settings in separate files (
/config/[environment]/settings.cfm) -
Document Custom Settings - Comment your custom settings in the configuration files
-
Use Consistent Naming - Follow Wheels naming conventions for custom settings
-
Verify Before Deployment - Always check settings for the target environment before deploying
-
Sensitive Data - Keep sensitive settings (API keys, passwords) in environment variables or
.envfiles
Integration with Other Commands
Section titled “Integration with Other Commands”Works well with other Wheels CLI commands:
# Check environment, then settingswheels get environmentwheels get settings
# Verify cache settings before clearing cachewheels get settings cachewheels clear cache
# Check database settings before running migrationswheels get settings dataSourceNamewheels 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
trueorfalse - Complex values (arrays, structs) show a summary
- The command shows which environment’s settings are being displayed
Troubleshooting
Section titled “Troubleshooting”Settings Not Showing Expected Values
Section titled “Settings Not Showing Expected Values”- Check which environment is active:
wheels get environment - Verify the settings file exists in the correct location
- Check for syntax errors in your settings files
- Ensure settings use the correct
set()function syntax
Missing Settings
Section titled “Missing Settings”If expected settings are missing:
- Verify they’re defined using
set()function - Check file paths:
/config/settings.cfmand/config/[environment]/settings.cfm - Ensure no syntax errors prevent parsing
Filter Not Working
Section titled “Filter Not Working”- Remember the filter is case-insensitive
- The filter matches any part of the setting name
- Use more specific terms for precise filtering
Limitations
Section titled “Limitations”- 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