Project settings

Settings holds the handful of things that belong to the whole project rather than to one stage or one sandbox.

Annotated screenshot of Project Settings: a "Project Information" card showing Project Name, Git Repository and Region, and below it a red-bordered "Danger Zone" card with a "Delete project" action. Callout: "Project-wide settings, and the one irreversible action."

Project information

• Project name — what the project is called in the console. It's also the basis for your project's URL slug, so it's worth getting right early.
• Git repository — the repository Pikku Studio Cloud commits your code to and deploys from. If nothing is connected yet, this says so.
• Region — where your project runs. Set when the project is created.

Most day-to-day configuration isn't here, because it belongs to a stage rather than the project. Environment variables and secrets are per-stage; custom domains attach to a stage; members and roles belong to your organization.

Danger zone

Deleting a project permanently removes it along with every deployment and everything stored in it. It cannot be undone, so the action asks you to type the project's name to confirm rather than just clicking through a dialog.

If what you actually want is to stop a stage, remove that stage from Branches instead — that leaves the project and its other stages alone.

Where to go next

• Stages & branches — the per-stage settings that aren't here.
• Members — who can reach this project, managed at the organization level.
• Billing — plan and payment, also organization-level.