Configuration

Environment variables, profiles, and where secrets belong.

Configuration layers

Effective configuration is usually built in this order:

1. Defaults shipped with the kit or framework

2. Profile selection (for example default, staging, production)

3. Secrets from your vault or host env (never committed)

Standard kits expose runtime settings through env variables or documented profile fields. If your artifact documents a different precedence, follow the artifact.

Secrets and keys

Never commit venue keys, signing material, or database URLs to git. Use your platform’s secret store or inject at deploy time.

Profiles

Use named profiles to separate dry-run, staging, and production without editing files on the server. Keep profile names aligned with your deploy pipeline so rollback means switching artifact + env, not hand-editing live boxes.

Related

• Installation

• Dry run

• Deployment

• License file format (v1) (offline .lic verification)