Configuration Commands

The configuration commands help you manage and inspect your Azu CLI configuration.

azu config:show

Display the current configuration settings.

Usage

azu config:show [options]

Options

Option
Description
Default

--format, -f

Output format (yaml/json/table)

yaml

--env, -e

Environment to show

current

--section, -s

Show specific section only

all

Sections

  • global - Global CLI settings (debug mode, verbose, quiet)

  • project - Project configuration (name, path, database adapter)

  • server - Development server settings (host, port, watch)

  • database - Database configuration (host, port, user, name)

  • paths - File paths (templates, output)

  • logging - Logging configuration (level, format)

Examples

azu config:validate

Validate your configuration files and settings.

Usage

Options

Option
Description
Default

--env, -e

Environment to validate

current

--strict

Treat warnings as errors

false

--config, -c

Path to configuration file

auto

What Gets Validated

  • Configuration file syntax (YAML)

  • Project directory structure

  • Database configuration (adapter, port range)

  • Server configuration (port range, host)

  • Path existence (templates, output)

Examples

azu config:env

Manage environment variables used by Azu CLI.

Usage

Options

Option
Description

--list

List all known environment variables

--show

Show current values

--set

Set a variable (VAR=VALUE)

--unset

Remove a variable

Environment Variables

Variable
Description

AZU_ENV

Environment name

AZU_DEBUG

Enable debug mode

AZU_VERBOSE

Enable verbose output

AZU_QUIET

Suppress non-error output

AZU_HOST

Development server host

AZU_PORT

Development server port

AZU_DB_HOST

Database host

AZU_DB_PORT

Database port

AZU_DB_USER

Database user

AZU_DB_PASSWORD

Database password

AZU_DB_NAME

Database name

DATABASE_URL

Full database connection URL

Examples

Best Practices

1. Validate Before Deploying

Always validate your configuration before deploying to production:

2. Use Environment Variables for Secrets

Never commit secrets to version control. Use environment variables:

3. Review Configuration Regularly

Periodically review your configuration to ensure it's optimized:


See Also:

Last updated