CONFIGURATION

Environments & secrets

RAIQL 1.0 separates environment intent from secret values. Source declares names and profiles; local values live under .raiql/env and are ignored by Git.

Declare profiles

ENVIRONMENT development, staging, production;

Profiles are normalized to lowercase and become part of raiql.env.json. They do not contain values.

Declare required secrets

SECRET DATABASE_URL, RAIQL_JWT_SECRET, PAYMENT_API_KEY;

Only secret names enter the IR. RAIQL never accepts secret values in source.

Initialize local values

terminal

raiql env list
raiql env init development
raiql env check development

Local profiles are stored in .raiql/env/<profile>.env, which new projects ignore in Git.

Run with a profile

terminal

raiql dev --env development
raiql test --env staging
raiql build --env production

The CLI loads the selected profile into child processes without rewriting the generated project's .env file.

Generated contract

Every generated target contains raiql.env.json, profile-specific example files and scripts/check-env.mjs. Server targets also receive lib/raiql-env.ts so generated runtime code can reject unresolved required values.

Continue exploring RAIQLOpen the playground →