Environments

Adding, configuring, and deleting environments. Default Preview / Production setup, plus custom environments for staging and per-team.

Every project starts with two environments: Preview (auto-deploys every change) and Production (manually promoted). You can add more — staging, QA, per-team — as needed.

Default environments

Environment	Triggered by	Visible at
Preview	Every prompt or hand-edit	*.vly.app
Production	Manual promotion	Custom domain (or *.vly.app if not configured)

Adding a custom environment

1. Settings → Environments → Add environment

   Pick a name (staging, qa, demo-acme).

2. Configure secrets per environment

   Each environment has its own secrets store. Stripe test keys in staging; live in production.

3. Promote into the environment

   From any preview, click “Promote to [env name]”.

4. (Optional) Add a domain

   staging.yourapp.com → CNAME to the staging environment.

Per-environment differences

What can vary between environments:

	Yes
Secrets	✓
Custom domain	✓
Indexing (X-Robots-Tag: noindex for non-prod)	✓
Analytics destination (GA4 test vs prod property)	✓
Feature flags	✓ (via env-aware code)

What can’t:

	No
Schema	All environments share the same schema
Codebase	Same code; differences are env-driven

For schema differences across environments, use branching instead of environments.

Deleting an environment

Settings → Environments → [env] → Delete. Removes the environment, its secrets, and (if attached) the custom domain. Other environments are unaffected.

Related

Environment variables

Setting per-environment env vars.

Secrets

Secret-store mechanics.

Staging vs production

Promotion patterns.