Environments

An environment is one running copy of a project. Each has its own deployments, environment variables and domains, so staging can run another version, with other settings, next to production.

Production

Every project starts with production. It's the environment:

• the CLI deploys to;
• served at <slug>.hiraiship.app, a domain that can't be removed.

It stays the production environment for the project's whole life: it can be renamed, but not replaced by another environment, and not deleted on its own. Deleting the project is the only way it goes.

Other environments

A project can have more environments, up to your plan's limit:

Names use lowercase letters, digits and hyphens: staging, preview, qa.

An environment you add has no hiraiship.app address: add a custom domain and point it at the environment, staging.example.com for instance.

Renaming and deleting

Manage environments from the project's Settings, in the Environments tab.

• Renaming changes the name only. The environment keeps its deployments, domains and variables.
• Deleting an environment other than production takes it offline at once. Its domains, environment variables and queued builds are deleted, and this can't be undone. Its usage this month stays on the bill.

Through the API, it's DELETE /environments/:environmentId: the production environment answers 409 with code: production_environment.

Live environments

An environment is live when it has a deployment serving traffic and isn't paused or hibernated. Plans include a number of live environments across the workspace:

• On Free, it's a hard limit: a build that would bring one more environment live is refused. Redeploying an environment that's already live never is.
• On a paid plan, environments past the included number are billed per day.

An environment nobody visits stops counting once it's paused or hibernated.