Environments

What it is

Each project has one or more environments. Every project is created with a prod environment automatically. Paid tiers can add non-prod environments up to their plan’s cap.

An environment owns:

• its own apps (deployments)
• its own databases
• its own env vars (per app)
• its own custom domains

Apps in different environments are independent — a failed deploy in staging does not affect prod.

Naming

Environment names are lowercase, 1–32 characters, [a-z0-9-]. Names prod, api, admin, auth, www are reserved.

Default domains

• Prod: {slug}.run.uploy.eu
• Non-prod: {slug}-{envName}.run.uploy.eu

Both are covered by the same *.run.uploy.eu wildcard TLS certificate.

Tier caps

See Plans and caps.

API

• GET /api/projects/{projectID}/environments
• POST /api/projects/{projectID}/environments
• GET /api/projects/{projectID}/environments/{envID}
• DELETE /api/projects/{projectID}/environments/{envID}

All app, database, and env-var routes nest beneath /environments/{envID}/.... Legacy flat paths 301-redirect to the prod env for one release.

Related

• Add a staging environment