#Environment Variables

Continuwuity can be configured entirely through environment variables, making it ideal for containerised deployments and infrastructure-as-code scenarios.

This is a convenience reference and may not be exhaustive. The Configuration Reference is the primary source for all configuration options.

#Prefix System

Continuwuity supports three environment variable prefixes for backwards compatibility:

• CONTINUWUITY_* (current, recommended)
• CONDUWUIT_* (compatibility)
• CONDUIT_* (legacy)

All three prefixes work identically. Use double underscores (__) to represent nested configuration sections from the TOML config.

Examples:

# Simple top-level config
CONTINUWUITY_SERVER_NAME="matrix.example.com"
CONTINUWUITY_PORT="8008"

# Nested config sections use double underscores
# This maps to [database] section in TOML
CONTINUWUITY_DATABASE__PATH="/var/lib/continuwuity"

# This maps to [tls] section in TOML
CONTINUWUITY_TLS__CERTS="/path/to/cert.pem"

#Configuration File Override

You can specify a custom configuration file path:

• CONTINUWUITY_CONFIG - Path to continuwuity.toml (current)
• CONDUWUIT_CONFIG - Path to config file (compatibility)
• CONDUIT_CONFIG - Path to config file (legacy)

#Essential Variables

These are the minimum variables needed for a working deployment:

#Network Configuration

#Database Configuration

#Cache Configuration

#DNS Configuration

Configure DNS resolution behaviour for federation and external requests.

#Request Configuration

#Federation Configuration

Control how your server federates with other Matrix servers.

Example:

# Trust matrix.org for key verification
CONTINUWUITY_TRUSTED_SERVERS='["matrix.org"]'

#Registration & User Configuration

Control user registration and account creation behaviour.

Example:

# Disable open registration
CONTINUWUITY_ALLOW_REGISTRATION="false"

# Require a registration token
CONTINUWUITY_REGISTRATION_TOKEN="your_secret_token_here"

#Feature Configuration

#TLS Configuration

Built-in TLS support is primarily for testing. For production deployments, especially when federating on the internet, use a reverse proxy (Traefik, Caddy, nginx) to handle TLS termination.

Example (testing only):

CONTINUWUITY_TLS__CERTS="/etc/letsencrypt/live/matrix.example.com/fullchain.pem"
CONTINUWUITY_TLS__KEY="/etc/letsencrypt/live/matrix.example.com/privkey.pem"

#Logging Configuration

Control log output format and verbosity.

Examples:

# Set log level to info
CONTINUWUITY_LOG="info"

# Enable debug logging for specific modules
CONTINUWUITY_LOG="warn,continuwuity::api=debug"

# Disable colours for log aggregation
CONTINUWUITY_LOG_COLORS="false"

#Observability Configuration

#Admin Configuration

Configure admin users and automated command execution.

Examples:

# Create admin user on startup
CONTINUWUITY_ADMIN_EXECUTE='["users create-user admin", "users make-user-admin admin"]'

# Specify admin users directly
CONTINUWUITY_ADMINS_LIST='["@alice:example.com", "@bob:example.com"]'

#Media & URL Preview Configuration

#Tokio Runtime Configuration

These can be set as environment variables or CLI arguments:

#See Also

• Configuration Reference - Complete TOML configuration documentation
• Admin Commands - Admin command reference