Skip to main content

Configuration

Supply startup configuration through the release bundle's environment file or your Helm values. Manage installation settings in Settings → Administration, using a normal TestVibe account with instance-administrator access.

The configuration model​

The deployment supplies database and service credentials, storage mounts, and network wiring. Administration manages optional email, sign-in, model providers, capacity, and licensing. Host-managed values appear locked in the application; change them in the deployment. Follow any restart prompt after saving.

Most secret values support a mounted file through the corresponding _FILE variable. Check the release's .env.example for support for each individual setting.

Required values​

For Compose, copy .env.example to .env and supply strong, different values for:

  • TV_PG_PASSWORD: PostgreSQL password.
  • TV_BLOBSERVER_SIGNING_KEY: artifact URL signing key.
  • TV_BLOBSERVER_ADMIN_KEY: server-to-server artifact access.
  • TV_RUNNER_KEY: runner and browser service authentication.

Set TESTVIBE_PUBLIC_BASE_URL and TV_BLOBSERVER_PUBLIC_URL to addresses your users' browsers can reach. See installation for Helm equivalents and HTTPS and reverse proxies.

Create the first administrator through normal application signup. The old TV_ADMIN_PASSWORD and first-user console are not part of current customer deployments.

Preserve an existing TESTVIBE_SECRET_PROTECTION_KEY exactly. On a new Compose or Kubernetes installation, leave it unset: the app creates its protection key in PostgreSQL. The appliance generates and preserves its configuration on the data disk. Back up the database, artifacts, and secret configuration together. See backup and restore.

Optional integrations​

Billing is off on-prem​

Self-hosted installations do not use TestVibe Cloud credits. Your AI provider can still charge for its services. Your license and configured capacity limits continue to apply.