Projects and Environments
Split your work into projects and environments.
Concepts explains what projects and environments are. This page is about managing them.
Projects
Create one from the team page. Give it a name, or leave the field empty and Unbind makes one up. Names are unique within a team and can be up to 32 characters.
Every new project starts with an environment called production.
Project > Settings has:
- General: rename the project and change its description.
- Environments: add, rename and delete environments.
- Variables: values shared by the project's services. See Variables.
- Webhooks: notifications about services and deployments. See Webhooks.
- Danger Zone: delete the project.
Finding and ordering projects
The search box on the team page filters projects by name. The sort button next to it switches between:
- Custom: the order your team arranged. This is the default.
- Newest First and Oldest First: by creation date.
- A → Z and Z → A: by name.
To arrange projects, keep the sort on Custom, clear the search, and drag a card to its new place. Pressing and holding a card also picks it up, and on a phone you hold it first. With a keyboard, focus a card, press Space, move it with the arrow keys and press Space again.
The custom order is shared: everyone in the team sees the same one. Changing it needs the editor role. New projects go to the top.
Through the API, list-projects lists newest first unless you pass sort_by (custom, name, created_at or updated_at) and sort_order. reorder-projects sets the custom order.
Environments
Add one under Settings > Environments. It starts empty. There is no way to copy an environment yet, so you add its services again, or script it through the API.
Switch between environments with the environment picker at the top of the project. The Services, Logs and Metrics tabs always show the one you picked.
A common setup:
production: deploys frommain.staging: the same services, deploying from astagingbranch, with their own database and their own variables.
Environments share nothing. Each has its own services, databases, volumes and variables, which is what makes staging safe to break.
Deleting
Deleting takes the data with it
Deleting an environment permanently deletes its services, databases and volumes. Deleting a project does that for every environment inside it. Neither can be undone.
- A project's last environment cannot be deleted. Delete the project instead.
- Deleting needs the admin role.