wheels env

Base command for environment management in Wheels applications.

Usage

wheels env [subcommand]

Description

The wheels env command provides environment management for Wheels applications. It handles environment configuration, switching between environments, and managing environment-specific settings.

Subcommands

Command	Description
list	List all configured environments
setup	Setup a new environment
switch	Switch to a different environment

Direct Usage

When called without subcommands, displays help information:

wheels env

Output:

🌍 Wheels Environment Management

Available commands:

  wheels env list
    List all configured environments

  wheels env setup <environment>
    Setup a new environment (development, staging, production)
    Options: --template=docker --database=postgres

  wheels env switch <environment>
    Switch to a different environment

Examples:
  wheels env setup development
  wheels env setup production --template=docker --database=postgres
  wheels env switch staging

Examples

List all environments

wheels env list

Setup new environment

wheels env setup development
wheels env setup production --template=docker --database=postgres

Switch environment

wheels env switch production

Environment Configuration

Each environment has its own configuration:

/config/
  ├── development/
  │   └── settings.cfm
  ├── testing/
  │   └── settings.cfm
  ├── production/
  │   └── settings.cfm
  └── environment.cfm

Environment Variables

The command respects these environment variables:

Variable	Description	Default
WHEELS_ENV	Current environment	development
WHEELS_DATASOURCE	Database name	Per environment
WHEELS_DEBUG	Debug mode	Per environment

Environment Detection

Order of precedence:

1. Command line argument

2. WHEELS_ENV environment variable

3. .wheels-env file

4. Default (development)

Common Environments

Development

• Debug enabled

• Detailed error messages

• Hot reload active

• Development database

Testing

• Test database

• Fixtures loaded

• Debug enabled

• Isolated from production

Production

• Debug disabled

• Optimized performance

• Production database

• Error handling active

Staging

• Production-like

• Separate database

• Debug configurable

• Pre-production testing

Environment Files

.wheels-env

Local environment override:

production

.env.[environment]

Environment-specific variables:

# .env.production
DATABASE_URL=mysql://prod@host/db
CACHE_ENABLED=true
DEBUG_MODE=false

Integration

With Other Commands

Many commands respect current environment:

# Uses current environment's database
wheels dbmigrate latest

# Reloads in current environment
wheels reload

# Tests run in test environment
wheels test run

In Application Code

Access current environment:

<cfset currentEnv = get("environment")>
<cfif currentEnv eq "production">
    <!--- Production-specific code --->
</cfif>

Best Practices

1. Never commit .wheels-env file

2. Use testing environment for tests

3. Match staging to production closely

4. Separate databases per environment

5. Environment-specific configuration files

Use Cases

1. Local Development: Switch between feature environments

2. Testing: Isolated test environment

3. Deployment: Environment-specific configurations

4. Debugging: Quick environment switching

5. Team Development: Consistent environments

Notes

• Environment changes may require application restart

• Database connections are environment-specific

• Some settings only take effect after reload

• Use version control for environment configs

See Also

• wheels env setup - Setup new environment

• wheels env list - List environments

• wheels env switch - Switch environments

• wheels config - Configuration management